linux-kernel - Re: [git pull] core, x86: make LIST

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: <487BAC38.4060601@firstfloor.org>
Date:	Mon, 14 Jul 2008 21:42:48 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Avi Kivity <avi@...ranet.com>
Subject: Re: [git pull] core, x86: make LIST_POISON less deadly

Linus Torvalds wrote:
> 
> On Mon, 14 Jul 2008, Andi Kleen wrote:
>> How about if the page fault handler checks for the value and prints
>> a obvious string? It could do this reliably, unlike the "grep
>> all registers for poison on #GP" method that was earlier proposed.
> 
> The GP handler, you mean.

No i meant #PF because #PF can do it reliably (sorry wasn't fully
convinced by you earlier)

But ok doing it a little unreliably in #GP is better than nothing.

It would be cool if that function knew about the various poisons
in poison.h and printed them out by name.

That would indeed improve newbie friendliness of oopses significantly
I believe. Kind of like a mini AI in the oops printer.

I can look at that later if nobody beats me to it.

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