From: Alex Henrie <alexhenrie24@gmail.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Arjan van de Ven <arjanvandeven@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
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>,
Tyler Hicks <tyhicks@canonical.com>,
Al Viro <viro@zeniv.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arjan van de Ven <arjan@infradead.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH v2] x86: Preserve iopl on fork and execve
Date: Tue, 12 May 2015 12:05:45 -0600 [thread overview]
Message-ID: <CAMMLpeR-JZTTLGY6yovnHdz7esAvRMrMeSRpWAKyvgenREM24g@mail.gmail.com> (raw)
In-Reply-To: <5552209C.501@gmail.com>
2015-05-12 9:47 GMT-06:00 Austin S Hemmelgarn <ahferroin7@gmail.com>:
> On 2015-05-12 11:25, Arjan van de Ven wrote:
>> 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.
>
> Personally, I _really_ like this idea. The only thing I know of on any
> modern distro that even considers using ioperm is hwclock, and it only does
> so if it can't access the RTC through other means (and if you have an RTC,
> you really should have the /dev interface enabled).
Removing iopl might be OK. Removing ioperm would break my use case of
legacy code that needs direct access to the parallel port.
-Alex
next prev parent reply other threads:[~2015-05-12 18:06 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 [this message]
2015-05-12 18:12 ` Austin S Hemmelgarn
2015-05-14 10:41 ` Josh Triplett
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=CAMMLpeR-JZTTLGY6yovnHdz7esAvRMrMeSRpWAKyvgenREM24g@mail.gmail.com \
--to=alexhenrie24@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ahferroin7@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=arjanvandeven@gmail.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dougvj@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tyhicks@canonical.com \
--cc=viro@zeniv.linux.org.uk \
/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).