From: Avi Kivity <avi@qumranet.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] Make LIST_POISON less deadly (v3)
Date: Tue, 20 May 2008 18:17:59 +0300 [thread overview]
Message-ID: <4832EBA7.2040007@qumranet.com> (raw)
In-Reply-To: <87fxsdgg6f.fsf@basil.nowhere.org>
Andi Kleen wrote:
> Avi Kivity <avi@qumranet.com> writes:
>
>>
>> +config ILLEGAL_POINTER_VALUE
>> + hex
>> + default 0 if X86_32
>> + default 0xffffc10000000000 if X86_64
>>
>
> Don't make it exactly 0xffffc10000000000 but 0xffffc10000000000 + 0x1000000
> or so, otherwise list_entry() users which subtract offsets would still
> end up in user space and there might be actually something in there
> by default.
>
The poison code adds a large offset (>1MB) so we're safe here.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-05-20 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 11:39 [PATCH] Make LIST_POISON less deadly (v3) Avi Kivity
2008-05-20 11:55 ` Ingo Molnar
2008-05-20 15:15 ` Andi Kleen
2008-05-20 15:17 ` Avi Kivity [this message]
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=4832EBA7.2040007@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
/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