From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Avi Kivity <avi@qumranet.com>
Subject: Re: [git pull] core, x86: make LIST_POISON less deadly
Date: Mon, 14 Jul 2008 20:35:05 +0200 [thread overview]
Message-ID: <871w1wz546.fsf@basil.nowhere.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0807140758100.3305@woody.linux-foundation.org> (Linus Torvalds's message of "Mon, 14 Jul 2008 08:03:16 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> Why not pick something that is *guaranteed* to fault? The above looks like
> any future setup that supports 41 bits of addressing and has extended the
> page tables (yes, it will happen eventually) will find that to be a
> perfectly valid address?
When that happens then it will be either unmapped (and fault anyways)
or the kernel has to be changed to 5 level page tables first and then
surely the poison value could change too.
-Andi
next prev parent reply other threads:[~2008-07-14 18:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 14:48 [git pull] core, x86: make LIST_POISON less deadly Ingo Molnar
2008-07-14 15:03 ` Linus Torvalds
2008-07-14 15:12 ` Ingo Molnar
2008-07-14 15:53 ` Avi Kivity
2008-07-14 15:59 ` Linus Torvalds
2008-07-14 16:07 ` Ingo Molnar
2008-07-14 16:08 ` Avi Kivity
2008-07-14 16:26 ` Linus Torvalds
2008-07-14 16:34 ` Ingo Molnar
2008-07-14 18:33 ` Andi Kleen
2008-07-14 18:42 ` Linus Torvalds
2008-07-14 19:11 ` Andi Kleen
2008-07-14 19:30 ` Linus Torvalds
2008-07-14 19:42 ` Andi Kleen
2008-07-14 18:35 ` Andi Kleen [this message]
2008-07-14 18:42 ` Linus Torvalds
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=871w1wz546.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.