From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
William Lee Irwin III <wli@holomorphy.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: __supported_pte_mask breaks PROT_NONE pages
Date: Thu, 05 Feb 2009 10:00:35 -0800 [thread overview]
Message-ID: <498B2943.8000602@goop.org> (raw)
In-Reply-To: <20090205173050.GB24599@elte.hu>
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>> Ingo Molnar wrote:
>>
>>> btw., did you actually see a boot crash due to this, on a pre-PGE system?
>>>
>>>
>> No, under Xen, since it also disables PGE.
>>
>
> but it was a boot crash, right? Such info is useful in the first line of a
> commit message:
>
> Impact: fix non-PGE boot crash
>
> (that also makes it less likely that the commit is under-prioritized.)
It's not immediate; in early usermode. It only happens when using a
populated PROTNONE page, which is actually pretty rare, it seems -
perhaps made more common by the new mlock code. But, yes, it stopped my
machine from booting.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
William Lee Irwin III <wli@holomorphy.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: __supported_pte_mask breaks PROT_NONE pages
Date: Thu, 05 Feb 2009 10:00:35 -0800 [thread overview]
Message-ID: <498B2943.8000602@goop.org> (raw)
In-Reply-To: <20090205173050.GB24599@elte.hu>
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>> Ingo Molnar wrote:
>>
>>> btw., did you actually see a boot crash due to this, on a pre-PGE system?
>>>
>>>
>> No, under Xen, since it also disables PGE.
>>
>
> but it was a boot crash, right? Such info is useful in the first line of a
> commit message:
>
> Impact: fix non-PGE boot crash
>
> (that also makes it less likely that the commit is under-prioritized.)
It's not immediate; in early usermode. It only happens when using a
populated PROTNONE page, which is actually pretty rare, it seems -
perhaps made more common by the new mlock code. But, yes, it stopped my
machine from booting.
J
next prev parent reply other threads:[~2009-02-05 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 2:33 __supported_pte_mask breaks PROT_NONE pages Jeremy Fitzhardinge
2009-02-05 2:33 ` Jeremy Fitzhardinge
2009-02-05 5:40 ` H. Peter Anvin
2009-02-05 14:28 ` Ingo Molnar
2009-02-05 14:29 ` Ingo Molnar
2009-02-05 14:29 ` Ingo Molnar
2009-02-05 17:23 ` Jeremy Fitzhardinge
2009-02-05 17:23 ` Jeremy Fitzhardinge
2009-02-05 17:30 ` Ingo Molnar
2009-02-05 17:30 ` Ingo Molnar
2009-02-05 18:00 ` Jeremy Fitzhardinge [this message]
2009-02-05 18:00 ` Jeremy Fitzhardinge
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=498B2943.8000602@goop.org \
--to=jeremy@goop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wli@holomorphy.com \
--cc=xen-devel@lists.xensource.com \
/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.