[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1911141939010.29616@nanos.tec.linutronix.de>
Date: Thu, 14 Nov 2019 19:39:16 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Borislav Petkov <bp@...en8.de>
cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
Andy Lutomirski <luto@...nel.org>,
Linus Torvalds <torvalds@...uxfoundation.org>,
Stephen Hemminger <stephen@...workplumber.org>,
Willy Tarreau <w@....eu>, Juergen Gross <jgross@...e.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [patch V3 17/20] x86/iopl: Restrict iopl() permission scope
On Thu, 14 Nov 2019, Borislav Petkov wrote:
> On Wed, Nov 13, 2019 at 09:42:57PM +0100, Thomas Gleixner wrote:
> > +config X86_IOPL_EMULATION
> > + bool "IOPL Emulation"
> > + ---help---
> > + Legacy IOPL support is an overbroad mechanism which allows user
> > + space aside of accessing all 65536 I/O ports also to disable
> > + interrupts. To gain this access the caller needs CAP_SYS_RAWIO
> > + capabilities and permission from eventually active security
>
> I think you mean here: s/eventually/potentially/ or so. "eventually" is
> one of the false friends. :)
Fixed
Powered by blists - more mailing lists