linux-kernel - Re: [PATCH] x86_64: remove empty lines from stack traces/oopses

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: <20080815084934.7f56662e@infradead.org>
Date:	Fri, 15 Aug 2008 08:49:34 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Alexey Dobriyan <adobriyan@...il.com>, akpm@...l.org,
	mingo@...hat.com, linux-kernel@...r.kernel.org, ak@...e.de,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86_64: remove empty lines from stack traces/oopses

On Fri, 15 Aug 2008 17:25:55 +0200
Ingo Molnar <mingo@...e.hu> wrote:

> > Any recent oops with and without empty lines after Call trace: and 
> > after calltrace.
> 
> ok - i've queued up your fix in tip/x86/debug.
> 
> Arjan, can the removal of empty newlines break the kerneloops.org 
> parser?

nope is fine; the parser isn't that fragile against empty lines
(in fact they get filtered out ;-)


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/