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: <20080519190438.GB24599@uranus.ravnborg.org>
Date:	Mon, 19 May 2008 21:04:38 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Avi Kivity <avi@...ranet.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Make LIST_POISON less deadly

On Mon, May 19, 2008 at 04:45:03PM +0300, Avi Kivity wrote:
> Ingo Molnar 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.
> >  
> 
> Any idea how to override a value in Kconfig?  We can do it for bool 
> values but not strings.
> 
> e.g.
> 
> lib/Kconfig:
>  config ILLEGAL_POINTER_VALUE
>      hex
>      default 0
> 
> arch/x86/Kconfig:
>  config X86
>    select ILLEGAL_POINTER_VALUE=0x80000000000000000000000000 if X86_64
> 
> ?
> 
> I could do it with a boolean signifying existence and a hex for the 
> value, but I'd rather not.

Sorry - no help here. I have not tried to work that much with int in
Kconfig.

That said I really think stuff like this belongs in a header file.
I do not agree to hide this as part of the configuration.

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