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] [thread-next>] [day] [month] [year] [list]

Message-ID: <487B7A10.9050104@qumranet.com>
Date:	Mon, 14 Jul 2008 19:08:48 +0300
From:	Avi Kivity <avi@...ranet.com>
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>
Subject: Re: [git pull] core, x86: make LIST_POISON less deadly

Linus Torvalds wrote:
>> We dont do any instruction decoding in #GP handlers to figure out what 
>> happened, while in the pagefault case we know which address faulted, 
>> etc.
>>     
>
> Why would we care? It would be very obvious from the instruction 
> disassembly plus the register contents. No need to decode instructions.
>   

We could add a printk to the #GP handler that alerts the reader that a 
poisoned list is suspected, if we find the address pattern in one of the 
registers.

-- 
error compiling committee.c: too many arguments to function

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