Re: [PATCH] Make LIST_POISON less deadly
From: Sam Ravnborg
Date: Mon May 19 2008 - 15:04:16 EST
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.
> config ILLEGAL_POINTER_VALUE
> default 0
> 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
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/