From: Sasha Levin <sasha.levin@oracle.com>
To: Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: "security@kernel.org" <security@kernel.org>,
X86 ML <x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 2/3] x86/ldt: Make modify_ldt optional
Date: Tue, 21 Jul 2015 16:20:44 -0400 [thread overview]
Message-ID: <55AEA99C.3030608@oracle.com> (raw)
In-Reply-To: <06f4a63325ac221868770a8d63207d74b160df89.1437508486.git.luto@kernel.org>
On 07/21/2015 03:59 PM, Andy Lutomirski wrote:
> The modify_ldt syscall exposes a large attack surface and is
> unnecessary for modern userspace. Make it optional.
Since this a "default y" option I think we need to make the
implications of this a bit clearer.
Do we know what userspace would break?
Maybe add a WARN_ONCE() in a stub syscall?
Thanks,
Sasha
next prev parent reply other threads:[~2015-07-21 20:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 19:59 [PATCH v2 0/3] x86: modify_ldt improvement, test, and config option Andy Lutomirski
2015-07-21 19:59 ` [PATCH v2 1/3] x86/ldt: Make modify_ldt synchronous Andy Lutomirski
2015-07-21 21:53 ` Boris Ostrovsky
2015-07-21 23:38 ` Andrew Cooper
2015-07-22 0:07 ` Andy Lutomirski
2015-07-22 0:21 ` Andrew Cooper
2015-07-22 0:28 ` Andy Lutomirski
2015-07-22 0:49 ` Andrew Cooper
2015-07-22 1:06 ` Andy Lutomirski
2015-07-22 2:04 ` [Xen-devel] " Boris Ostrovsky
2015-07-22 2:13 ` Andy Lutomirski
2015-07-22 2:01 ` Brian Gerst
2015-07-22 2:12 ` Andy Lutomirski
2015-07-22 2:53 ` Brian Gerst
2015-07-22 4:22 ` Andy Lutomirski
2015-07-21 19:59 ` [PATCH v2 2/3] x86/ldt: Make modify_ldt optional Andy Lutomirski
2015-07-21 20:20 ` Sasha Levin [this message]
2015-07-21 20:27 ` Andy Lutomirski
2015-07-21 20:28 ` Brian Gerst
2015-07-21 20:34 ` Andy Lutomirski
2015-07-21 20:54 ` Brian Gerst
2015-07-22 6:06 ` Ingo Molnar
2015-07-22 6:23 ` Andy Lutomirski
2015-07-22 6:27 ` Ingo Molnar
2015-07-22 18:49 ` Andy Lutomirski
2015-07-22 12:34 ` Willy Tarreau
2015-07-21 19:59 ` [PATCH v2 3/3] selftests/x86, x86/ldt: Add a selftest for modify_ldt Andy Lutomirski
2015-07-21 22:02 ` Boris Ostrovsky
2015-07-21 22:34 ` Andy Lutomirski
2015-07-21 23:36 ` Willy Tarreau
2015-07-21 23:40 ` Andy Lutomirski
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=55AEA99C.3030608@oracle.com \
--to=sasha.levin@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=security@kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).