From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Alex Shi <alex.shi@intel.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Will Drewry <wad@chromium.org>, Julien Tinnes <jln@google.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Dan Rosenberg <drosenberg@vsecurity.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <borislav.petkov@amd.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
kernel-hardening@lists.openwall.com,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com
Subject: [kernel-hardening] Re: [PATCH v3] x86: use a read-only IDT alias on all CPUs
Date: Thu, 11 Apr 2013 04:50:14 -0700 [thread overview]
Message-ID: <m261ztxp55.fsf@firstfloor.org> (raw)
In-Reply-To: <20130411083634.GA11824@gmail.com> (Ingo Molnar's message of "Thu, 11 Apr 2013 10:36:34 +0200")
Ingo Molnar <mingo@kernel.org> writes:
>
> This looks very nice to me now. Peter, any objections?
it seems pointless without randomized main kernel text location, because
the IDT will be still at a known per kernel fixed writable location in
the direct mapping.
As long as such randomization is not there it just wastes a TLB entry.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Alex Shi <alex.shi@intel.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Will Drewry <wad@chromium.org>, Julien Tinnes <jln@google.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Dan Rosenberg <drosenberg@vsecurity.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <borislav.petkov@amd.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
kernel-hardening@lists.openwall.com,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com
Subject: Re: [PATCH v3] x86: use a read-only IDT alias on all CPUs
Date: Thu, 11 Apr 2013 04:50:14 -0700 [thread overview]
Message-ID: <m261ztxp55.fsf@firstfloor.org> (raw)
In-Reply-To: <20130411083634.GA11824@gmail.com> (Ingo Molnar's message of "Thu, 11 Apr 2013 10:36:34 +0200")
Ingo Molnar <mingo@kernel.org> writes:
>
> This looks very nice to me now. Peter, any objections?
it seems pointless without randomized main kernel text location, because
the IDT will be still at a known per kernel fixed writable location in
the direct mapping.
As long as such randomization is not there it just wastes a TLB entry.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-04-11 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 19:24 [kernel-hardening] [PATCH v3] x86: use a read-only IDT alias on all CPUs Kees Cook
2013-04-10 19:24 ` Kees Cook
2013-04-10 19:24 ` Kees Cook
2013-04-11 8:36 ` [kernel-hardening] " Ingo Molnar
2013-04-11 8:36 ` Ingo Molnar
2013-04-11 8:36 ` Ingo Molnar
2013-04-11 11:50 ` Andi Kleen
2013-04-11 11:50 ` Andi Kleen [this message]
2013-04-11 11:50 ` Andi Kleen
2013-04-11 13:03 ` [kernel-hardening] " H. Peter Anvin
2013-04-11 13:03 ` H. Peter Anvin
2013-04-11 13:03 ` H. Peter Anvin
2013-04-11 21:43 ` [tip:x86/kaslr] x86: Use " tip-bot for Kees Cook
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=m261ztxp55.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=alex.shi@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=borislav.petkov@amd.com \
--cc=drosenberg@vsecurity.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=jln@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=wad@chromium.org \
--cc=x86@kernel.org \
--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.