linux-kernel - Re: [PATCH v2 0/6] Merge ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 May 2012 14:47:20 -0700
From:	Anton Vorontsov <cbouatmailru@...il.com>
To:	Colin Cross <ccross@...roid.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Kees Cook <keescook@...omium.org>,
	Tony Luck <tony.luck@...el.com>, Arnd Bergmann <arnd@...db.de>,
	John Stultz <john.stultz@...aro.org>,
	Shuah Khan <shuahkhan@...il.com>, arve@...roid.com,
	Rebecca Schultz Zavin <rebecca@...roid.com>,
	Jesper Juhl <jj@...osbits.net>,
	Randy Dunlap <rdunlap@...otime.net>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Thomas Meyer <thomas@...3r.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Marco Stornelli <marco.stornelli@...il.com>,
	WANG Cong <xiyou.wangcong@...il.com>,
	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	kernel-team@...roid.com
Subject: Re: [PATCH v2 0/6] Merge ram_console into pstore

On Thu, May 17, 2012 at 11:42:29AM -0700, Colin Cross wrote:
[...]
> Other than my comment on logging console into a single record,
> Acked-by: Colin Cross <ccross@...roid.com>

Thanks!

> There is one feature that ram_console had but lost when I added
> persistent_ram, which would be nice to get back:  registering the
> platform driver before module_init, to allow it to log oopses that
> happen during device probing.  This requires changing module_init to
> postcore_initcall, and switching from platform_driver_probe to
> platform_driver_register because the platform device is not registered
> when the platform driver is registered.  Depending on what functions
> are __init, it may cause a cascading change from __init to __devinit
> as well.

Yep, I'll look into it.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/