linux-kernel - Re: [PATCH v11 5/5] x86/earlyprintk: Patch for testing earlyprintk

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]

Message-ID: <20150609161126.GH22105@pd.tnic>
Date:	Tue, 9 Jun 2015 18:11:26 +0200
From:	Borislav Petkov <bp@...e.de>
To:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:	Alexander Kuleshov <kuleshovmail@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Mark Rustad <mark.d.rustad@...el.com>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [PATCH v11 5/5] x86/earlyprintk: Patch for testing earlyprintk

On Tue, Jun 09, 2015 at 06:30:18PM +0300, Andy Shevchenko wrote:
> On Tue, 2015-06-09 at 17:11 +0600, Alexander Kuleshov wrote:
> > Signed-off-by: Alexander Kuleshov <kuleshovmail@...il.com>
> 
> Please, mark those patches as something like "[NOT TO APPLY]".
> 
> Or you may (if others have no objections) create a configuration option
> like CONFIG_TEST_EARLY_PRINTK and make this patch upstreamable.

I think this is too much. No need for it - it's not like you can
automatically test early printk - you need to go stare at dmesg. And
if you want to do that, you can sprinkle some early_printk() calls
yourself.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/