Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757149AbbFPRbN (ORCPT ); Tue, 16 Jun 2015 13:31:13 -0400 Received: from terminus.zytor.com ([198.137.202.10]:60875 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757110AbbFPRbE (ORCPT ); Tue, 16 Jun 2015 13:31:04 -0400 Message-ID: <55805D0B.6020309@zytor.com> Date: Tue, 16 Jun 2015 10:29:47 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Alex Henrie , One Thousand Gnomes , Kees Cook , Thomas Gleixner , Ingo Molnar , Tyler Hicks , Al Viro , Andy Lutomirski , Andrew Morton , Borislav Petkov , Peter Zijlstra , Arjan van de Ven , Denys Vlasenko , Brian Gerst , Linux Kernel Mailing List , Austin Hemmelgarn , Arjan van de Ven , Ingo Molnar Subject: Re: ioperm is kept on fork References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 829 Lines: 22 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/