From: "H. Peter Anvin" <hpa@zytor.com>
To: Alex Henrie <alexhenrie24@gmail.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Tyler Hicks <tyhicks@canonical.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andy Lutomirski <luto@kernel.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>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Austin Hemmelgarn <ahferroin7@gmail.com>,
Arjan van de Ven <arjanvandeven@gmail.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: ioperm is kept on fork
Date: Tue, 16 Jun 2015 10:29:47 -0700 [thread overview]
Message-ID: <55805D0B.6020309@zytor.com> (raw)
In-Reply-To: <CAMMLpeRz=nxZqLiYcMA1WN==S68SsFCd-WJ9q63yTxSqjHei6A@mail.gmail.com>
On 06/16/2015 09:42 AM, Alex Henrie wrote:
> Hi,
>
> Could one of you knowledgeable kernel developers comment on
> https://bugzilla.kernel.org/show_bug.cgi?id=99911 ? The man pages
> maintainer wants to know when this behavior changed.
>
I know that I wrote a program which required I/O privileges at some
point, and it called ioperm() in a setuid wrapper. This was in the late
90s. I suspect we'd have to do a bit of a deep dive to double-check;
the old ioperm() code which only supported the ISA port range to avoid
having to copy the bitmap might be good to look at.
-hpa
prev parent reply other threads:[~2015-06-16 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 16:42 ioperm is kept on fork Alex Henrie
2015-06-16 17:29 ` H. Peter Anvin [this message]
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=55805D0B.6020309@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ahferroin7@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexhenrie24@gmail.com \
--cc=arjan@infradead.org \
--cc=arjanvandeven@gmail.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--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=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 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.