From: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
To: Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
Kosuke Tatsukawa <tatsu-zZGIbrA41Td8UrSeD/g0lQ@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] x86: Fix kernel panic when booting with XD disabled in uEFI firmware
Date: Tue, 8 Dec 2015 21:56:05 +0100 [thread overview]
Message-ID: <20151208205605.GB16417@pd.tnic> (raw)
In-Reply-To: <CAGXu5jKF3fVc5rsU=+jRcoBGB+ZkeHjF6mmSeJN0SoP-MpFGow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Dec 08, 2015 at 12:30:06PM -0800, Kees Cook wrote:
> If we add this for not-nx, I would like to add it for not-rodata too.
The W+X thing?
I was under the impression we want to fix all those so that the ptdump
check doesn't fire anymore.
> I've never seen anyone actually use it. I was asked to include it out
> of fear of some kind of rogue imagined CPU configuration that mixed NX
> and non-NX capable CPUs in a single machine where the forced NX
> re-enablement code would cause problems. As you might imagine, I'm not
> aware of this case ever being an issue. ;)
Right. :)
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2015-12-08 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 23:58 [PATCH 1/2] x86: Fix kernel panic when booting with XD disabled in uEFI firmware Kosuke Tatsukawa
[not found] ` <17EC94B0A072C34B8DCF0D30AD16044A0288E2D7-9lrffkYxhwTt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2015-12-04 16:40 ` Matt Fleming
[not found] ` <20151204164057.GE2514-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-07 23:10 ` Kosuke Tatsukawa
[not found] ` <17EC94B0A072C34B8DCF0D30AD16044A0288EFC7-9lrffkYxhwTt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2015-12-08 12:25 ` Matt Fleming
[not found] ` <20151208122557.GA2518-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-08 14:19 ` Borislav Petkov
[not found] ` <20151208141946.GD27180-fF5Pk5pvG8Y@public.gmane.org>
2015-12-08 20:30 ` Kees Cook
[not found] ` <CAGXu5jKF3fVc5rsU=+jRcoBGB+ZkeHjF6mmSeJN0SoP-MpFGow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-08 20:39 ` H. Peter Anvin
2015-12-08 20:54 ` Borislav Petkov
[not found] ` <19122B57-8052-4A92-801E-03CC84E66F06-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2015-12-15 0:07 ` Andy Lutomirski
2015-12-08 20:56 ` Borislav Petkov [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=20151208205605.GB16417@pd.tnic \
--to=bp-gina5biwoiwzqb+pc5nmwq@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=tatsu-zZGIbrA41Td8UrSeD/g0lQ@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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