Groups > linux.kernel > #1166286 > unrolled thread

Re: ioperm is kept on fork

Started by	"H. Peter Anvin" <hpa@zytor.com>
First post	2015-06-16 19:40 +0200
Last post	2015-06-16 19:40 +0200
Articles	1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

  Re: ioperm is kept on fork "H. Peter Anvin" <hpa@zytor.com> - 2015-06-16 19:40 +0200

#1166286 — Re: ioperm is kept on fork

From	"H. Peter Anvin" <hpa@zytor.com>
Date	2015-06-16 19:40 +0200
Subject	Re: ioperm is kept on fork
Message-ID	<pC307-Sa-27@gated-at.bofh.it>

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]

csiph-web

Re: ioperm is kept on fork

Contents

#1166286 — Re: ioperm is kept on fork