From: Josh Triplett <josh@joshtriplett.org>
To: Arjan van de Ven <arjanvandeven@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Alex Henrie <alexhenrie24@gmail.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Kees Cook <keescook@chromium.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Doug Johnson <dougvj@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86: Preserve iopl on fork and execve
Date: Thu, 14 May 2015 03:41:28 -0700 [thread overview]
Message-ID: <20150514104127.GA31892@x> (raw)
In-Reply-To: <CADyApD2-J07zg7gfa+LrFbHB_p2gN5k2P+x7OTCW1_rybTkdQA@mail.gmail.com>
On Tue, May 12, 2015 at 08:25:59AM -0700, Arjan van de Ven wrote:
> > also the interesting question is:
> > can a process give up these perms?
> > otherwise it becomes a "once given, never gotten rid of" hell hole.
>
> If you look at a modern linux distro, nothing should need/use iopl and
> co anymore, so maybe an interesting
> question is if we can stick these behind a CONFIG_ option (default on
> of course for compatibility)... just like
> some of the /dev/mem like things are now hidable for folks who know
> they don't need them.
I have a patch series that does exactly that, compiling out the syscalls
as well as the underlying architecture-specific infrastructure. (Saves
quite a bit of space, too.)
It still needs some more detailed x86 architecture review. Peter, Ingo?
Would you be interested in taking (an updated version of) that patch
series for the next merge window?
- Josh Triplett
next prev parent reply other threads:[~2015-05-14 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 23:38 [PATCH v2] x86: Preserve iopl on fork and execve Alex Henrie
2015-05-12 6:40 ` Ingo Molnar
2015-05-12 15:13 ` Linus Torvalds
2015-05-12 18:24 ` H. Peter Anvin
2015-05-12 15:24 ` Arjan van de Ven
2015-05-12 15:25 ` Arjan van de Ven
2015-05-12 15:47 ` Austin S Hemmelgarn
2015-05-12 18:05 ` Alex Henrie
2015-05-12 18:12 ` Austin S Hemmelgarn
2015-05-14 10:41 ` Josh Triplett [this message]
2015-05-15 0:52 ` H. Peter Anvin
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=20150514104127.GA31892@x \
--to=josh@joshtriplett.org \
--cc=alexhenrie24@gmail.com \
--cc=arjanvandeven@gmail.com \
--cc=dougvj@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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).