linux-kernel - Re: [PATCH/RFC] Make sure linux_banner is the first message in log

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, 22 May 2012 22:55:12 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	anton.vorontsov@...aro.org
Cc:	torvalds@...ux-foundation.org, ccross@...roid.com,
	gregkh@...uxfoundation.org, keescook@...omium.org,
	tony.luck@...el.com, arnd@...db.de, john.stultz@...aro.org,
	shuahkhan@...il.com, arve@...roid.com, rebecca@...roid.com,
	jj@...osbits.net, rdunlap@...otime.net, sboyd@...eaurora.org,
	thomas@...3r.de, akpm@...ux-foundation.org,
	marco.stornelli@...il.com, 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, mingo@...e.hu, a.p.zijlstra@...llo.nl,
	rusty@...tcorp.com.au
Subject: Re: [PATCH/RFC] Make sure linux_banner is the first message in
 log_buf

From: Anton Vorontsov <anton.vorontsov@...aro.org>
Date: Tue, 22 May 2012 19:35:16 -0700

> For scripting it is important to have a consistent header that tells
> where the kernel log starts. At least to me it always seemed that
> linux_banner served this purpose.

Your change will not achieve this goal, many architectures
print things long before control passes to init/main.c
--
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/