linux-kernel - Re: [PATCH 7/8] pstore/ram: Make tracing log versioned

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:	Tue, 17 Jul 2012 09:56:01 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Anton Vorontsov <anton.vorontsov@...aro.org>
Cc:	Kees Cook <keescook@...omium.org>,
	Colin Cross <ccross@...roid.com>,
	Tony Luck <tony.luck@...el.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, devel@...verdev.osuosl.org,
	linaro-kernel@...ts.linaro.org, Arnd Bergmann <arnd@...db.de>,
	patches@...aro.org, Marco Stornelli <marco.stornelli@...il.com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	linux-kernel@...r.kernel.org, arve@...roid.com,
	Jesper Juhl <jj@...osbits.net>,
	John Stultz <john.stultz@...aro.org>,
	Shuah Khan <shuahkhan@...il.com>,
	Rebecca Schultz Zavin <rebecca@...roid.com>,
	WANG Cong <xiyou.wangcong@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kernel-team@...roid.com, Thomas Meyer <thomas@...3r.de>
Subject: Re: [PATCH 7/8] pstore/ram: Make tracing log versioned

On Mon, Jul 09, 2012 at 05:10:45PM -0700, Anton Vorontsov wrote:
> Decoding the binary trace w/ a different kernel might be troublesome
> since we convert addresses to symbols. For kernels with minimal changes,
> the mappings would probably match, but it's not guaranteed at all.
> (But still we could convert the addresses by hand, since we do print
> raw addresses.)
> 
> If we use modules, the symbols could be loaded at different addresses
> from the previously booted kernel, and so this would also fail, but
> there's nothing we can do about it.
> 
> Also, the binary data format that pstore/ram is using in its ringbuffer
> may change between the kernels, so here we too must ensure that we're
> running the same kernel.
> 
> So, there are two questions really:
> 
> 1. How to compute the unique kernel tag;
> 2. Where to store it.
> 
> In this patch we're just passing linux_banner through CRC32.

That's nice, but it breaks the build on my system as linux_banner
somehow isn't enabled as part of the build?

Is there something else you can use?  Or fix the build to work properly?

I'll take the previous patches in the series, but I obviously can't take
this one because of the build error, sorry.

greg k-h
--
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/