From: Arjan van de Ven <arjan@linux.intel.com>
To: Thomas Garnier <thgarnie@google.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Kees Cook <keescook@chromium.org>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@kernel.org>, Dave Hansen <dave@sr71.net>,
Chen Yucong <slaoub@gmail.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Michael Ellerman <mpe@ellerman.id.au>,
Juergen Gross <jgross@suse.com>,
Richard Weinberger <richard@nod.at>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location
Date: Thu, 5 Jan 2017 10:56:45 -0800 [thread overview]
Message-ID: <563d8e71-b119-f76d-3784-20f24e43f44d@linux.intel.com> (raw)
In-Reply-To: <CAJcbSZFjurkb7dpN40XpVQLziQVxPWCt9iRfnzbRa+TWYTdq8w@mail.gmail.com>
On 1/5/2017 8:40 AM, Thomas Garnier wrote:
> Well, it happens only when KASLR memory randomization is enabled. Do
> you think it should have a separate config option?
no I would want it a runtime option.... "sgdt from ring 3" is going away
with UMIP (and is already possibly gone in virtual machines, see
https://lwn.net/Articles/694385/) and for those cases it would be a shame
to lose the randomization
next prev parent reply other threads:[~2017-01-05 18:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 22:16 [RFC] x86/mm/KASLR: Remap GDTs at fixed location Thomas Garnier
2017-01-05 8:11 ` Ingo Molnar
2017-01-05 15:08 ` Arjan van de Ven
2017-01-05 16:40 ` Thomas Garnier
2017-01-05 18:56 ` Arjan van de Ven [this message]
2017-01-05 19:00 ` Thomas Garnier
2017-01-06 17:44 ` Borislav Petkov
2017-01-06 18:04 ` Thomas Garnier
2017-01-05 16:39 ` Thomas Garnier
2017-01-06 6:34 ` Ingo Molnar
2017-01-05 17:51 ` Andy Lutomirski
2017-01-05 17:54 ` Thomas Garnier
2017-01-05 18:01 ` Andy Lutomirski
2017-01-05 18:35 ` Thomas Garnier
2017-01-05 18:58 ` Arjan van de Ven
2017-01-05 19:03 ` Thomas Garnier
2017-01-05 20:18 ` Andy Lutomirski
2017-01-05 21:08 ` Thomas Garnier
2017-01-05 21:19 ` Andy Lutomirski
2017-01-05 21:58 ` Thomas Garnier
2017-01-06 6:49 ` Ingo Molnar
2017-01-06 18:03 ` Thomas Garnier
2017-01-06 21:59 ` Andy Lutomirski
2017-01-06 22:54 ` Thomas Garnier
2017-01-06 23:39 ` Andy Lutomirski
2017-01-07 7:45 ` Ingo Molnar
2017-01-07 15:58 ` Andy Lutomirski
2017-01-07 7:35 ` Ingo Molnar
2017-01-07 16:02 ` Andy Lutomirski
2017-01-09 22:32 ` Thomas Garnier
2017-01-10 10:27 ` Ingo Molnar
2017-01-10 17:13 ` Thomas Garnier
2017-01-05 23:05 ` Linus Torvalds
2017-01-05 23:16 ` Thomas Garnier
2017-01-06 2:34 ` Andy Lutomirski
2017-01-06 18:02 ` Thomas Garnier
2017-01-06 21:53 ` Andy Lutomirski
2017-01-07 7:46 ` Ingo Molnar
2017-01-06 6:45 ` Ingo Molnar
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=563d8e71-b119-f76d-3784-20f24e43f44d@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave@sr71.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paul.gortmaker@windriver.com \
--cc=richard@nod.at \
--cc=slaoub@gmail.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).