linux-kernel - Re: [PATCH 2/2] [RFC] x86: Make page fault oopses similar

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1200951306.16972.28.camel@brick>
Date:	Mon, 21 Jan 2008 13:35:06 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] [RFC] x86: Make page fault oopses similar

On Mon, 2008-01-21 at 13:29 -0800, Arjan van de Ven wrote:
> On Mon, 21 Jan 2008 13:20:46 -0800
> Harvey Harrison <harvey.harrison@...il.com> wrote:
> 
> > Introduce printk_address to X86_32 in a simplified form for
> > now.  Reformat X86_64 printk_address to avoid two declarations.
> > 
> > Change the printk formats on X86_32 and 64 to be similar.
> 
> I'm not entirely convinced on this; I need to look closer but it appears the 32 bit version 
> doesn't use the "reliable" argument to print a ? in front of the dubious backtrace entries;
> that would be sort of a step backwards; (
> 

Sorry, I should have made it clearer that this was more for discussion
of the actual formatting.

printk_address needs to be ported to X86_32, the one in this patch
is just a placeholder.  Looking at the X86_64 version it looks like
it can be brought straight across, but I haven't tested that yet.

Harvey

--
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/