linux-kernel - Re: [PATCH] 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: <48318209.9060101@qumranet.com>
Date:	Mon, 19 May 2008 16:35:05 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Make LIST_POISON less deadly

Ingo Molnar wrote:
> * Avi Kivity <avi@...ranet.com> wrote:
>
>   
>>> i'd suggest to add an ARCH_ILLEGAL_POINTER define instead, which 
>>> defaults to zero and gets added to pointer-ish poison values. That 
>>> makes it both simpler and also it does not need any include/asm 
>>> changes because ARCH_ILLEGAL_POINTER can be set from the Kconfig 
>>> space.
>>>       
>> Right.
>>
>> How much unmapped space do we have on i386 or other archs?  The deltas 
>> added to ARCH_ILLEGAL_POINTER will have to be limited to that.
>>     
>
> can we get away with having the offset default to zero, and all poison 
> values remain unchanged if that? Then 64-bit x86 could just set the 
> offset to 2^63 and we wont have to worry about 32-bit x86 at all ...
>
> i.e. start small with this and only have an effect on 64-bit x86.
>   

Sure, will post an updated patch.

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