linux-kernel - Re: [PATCH 03/14] pstore/ram_core: Do not reset restored zone's position and size

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] [day] [month] [year] [list]

Message-ID: <20120522131938.GA26111@lizard>
Date:	Tue, 22 May 2012 06:19:38 -0700
From:	Anton Vorontsov <anton.vorontsov@...aro.org>
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 03/14] pstore/ram_core: Do not reset restored zone's
 position and size

On Fri, May 18, 2012 at 04:42:03PM -0700, Colin Cross wrote:
[...]
> This causes an interesting behavior change in the console logging.
> Before this change, the console log would show only the messages from
> the last reboot.  After this change, the console log will have logs
> from multiple boots appended to each other.

Heh. A nice feature, but frankly speaking, that wasn't my intent to
introduce it. :-)

I will document the new behaviour in the patch description.

> I can think of some
> places where that could very handy, so I'm not against the change, but
> as is it makes reading the logs much harder - the first oops you see
> while skimming the log may not be from the last reboot.
> 
> One possibility would be to insert an obvious (and script parseable)
> header during probe to separate the boots.

Yep, we have it already, i.e. linux_banner. This script should be
reliable enough:

	tac ramoops-console | sed '/^Linux version.*(.*@.*)/ q' | tac

> Another option would be to
> expand the ringbuffer metadata to contain duplicate start and size
> fields that only cover the most recent reboot, and export two files,
> console-ramoops that contains the last log, and console-all-ramoops
> that contains all the logs.

This seems like an overkill. :-)

> Or you could just zap the console buffer
> at boot to keep the old behavior.

Well, I actually like the new behaviour, so assuming that we're all
happy with the new feature, there's no need to zap it at boot. Or
we can at least make it configurable...

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/