Re: 2.2.0p7: fix to ioperm() ranges also needed

H. Peter Anvin (hpa@transmeta.com)
12 Jan 1999 19:53:22 GMT


Followup to: <Pine.LNX.3.96.990111221729.13448A-100000@ferret.lmh.ox.ac.uk>
By author: Chris Evans <chris@ferret.lmh.ox.ac.uk>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> The pre-patch for 2.2.0p7 includes a fix I suggest so that an iopl(3)
> process can drop privs to iopl(0) without needing to be root to do so!
>
> As a complementary fix, processes should probably always be allowed to use
> ioperm() if they specify 0 as the "set" argument.
>
> Cheers
> Chris
>
> P.S. Offtopic. Can someome clarify for me the differences between iopl(1),
> iopl(2) and iopl(3)? Thank you!
>

On Linux/i386, only iopl(3) matters. A process is I/O privileged if
IOPL >= CPL. A Linux user-space process has CPL 3.

-hpa

-- 
    PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD  1E DF FE 69 EE 35 BD 74
    See http://www.zytor.com/~hpa/ for web page and full PGP public key
        I am Bahá'í -- ask me about it or see http://www.bahai.org/
   "To love another person is to see the face of God." -- Les Misérables

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