From: Avi Kivity <avi@qumranet.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make LIST_POISON less deadly
Date: Mon, 19 May 2008 16:18:35 +0300 [thread overview]
Message-ID: <48317E2B.2030304@qumranet.com> (raw)
In-Reply-To: <20080519130151.GE13546@elte.hu>
Ingo Molnar wrote:
>
>> +/*
>> + * Define LIST_POISON[12] as pointers that cannot be dereferenced.
>> + */
>> +#ifdef CONFIG_X86_84
>> +# undef LIST_POISON1
>> +# undef LIST_POISON2
>> +# define LIST_POISON1 ((void *)0x8001000100010001L)
>> +# define LIST_POISON2 ((void *)0x8002000200020002L)
>> +#endif
>>
>
> 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.
Maybe have ARCH_ILLEGAL_POINTER_BASE and ARCH_ILLEGAL_POINTER_RANGE,
defaulting to 0 and (say) 4MB, and use the range to mask the deltas to
avoid overflows into legal pointer range.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-05-19 13:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 15:38 [PATCH] Make LIST_POISON less deadly Avi Kivity
2008-05-19 13:01 ` Ingo Molnar
2008-05-19 13:18 ` Avi Kivity [this message]
2008-05-19 13:22 ` Ingo Molnar
2008-05-19 13:35 ` Avi Kivity
2008-05-19 13:45 ` Avi Kivity
2008-05-19 19:04 ` Sam Ravnborg
2008-05-20 7:06 ` Avi Kivity
2008-05-20 11:24 ` Andi Kleen
2008-05-20 11:34 ` Avi Kivity
2008-05-20 11:49 ` Andi Kleen
2008-05-20 11:52 ` Avi Kivity
2008-05-20 12:04 ` Andi Kleen
2008-05-20 12:04 ` Ingo Molnar
2008-05-20 16:47 ` Pavel Machek
2008-05-20 16:50 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48317E2B.2030304@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox