Re: RFC: Tainting the kernel on raw I/O access

2014-09-04 Thread One Thousand Gnomes
On Thu, 4 Sep 2014 07:07:39 +0200 Ingo Molnar wrote: > > * H. Peter Anvin wrote: > > > In a meeting earlier today, we discussed MSR access and that it could be > > used to do bad things. The same applies to other forms of raw I/O > > (/dev/mem, /dev/port, ioperm, iopl, etc.) > > > > This is

Re: RFC: Tainting the kernel on raw I/O access

2014-09-04 Thread One Thousand Gnomes
> > As for the original purpose of taints, I'm not aware of any > > problems with MSR access or port IO causing excessive > > kernel oops reports. Are you? I'm not. From the bugzilla trends I don't think its a major cause, and we can usually root out the "user with dumb external module" problem a

Re: RFC: Tainting the kernel on raw I/O access

2014-09-04 Thread One Thousand Gnomes
On Wed, 03 Sep 2014 15:25:32 -0700 "H. Peter Anvin" wrote: > On 09/03/2014 03:20 PM, One Thousand Gnomes wrote: > > > > If you just want some "detector bits" for bug report filtering them its > > quite a different need to fixing "secure" boot mode. Even in the detector > > bits case there should

Re: RFC: Tainting the kernel on raw I/O access

2014-09-04 Thread Austin S Hemmelgarn
On 2014-09-03 19:46, Andi Kleen wrote: > "H. Peter Anvin" writes: > >> In a meeting earlier today, we discussed MSR access and that it could be >> used to do bad things. The same applies to other forms of raw I/O >> (/dev/mem, /dev/port, ioperm, iopl, etc.) > > I don't think it makes sense to u

Re: RFC: Tainting the kernel on raw I/O access

2014-09-03 Thread Ingo Molnar
* H. Peter Anvin wrote: > In a meeting earlier today, we discussed MSR access and that it could be > used to do bad things. The same applies to other forms of raw I/O > (/dev/mem, /dev/port, ioperm, iopl, etc.) > > This is basically the same problem with which the secure boot people > have bee

Re: RFC: Tainting the kernel on raw I/O access

2014-09-03 Thread Andi Kleen
"H. Peter Anvin" writes: > In a meeting earlier today, we discussed MSR access and that it could be > used to do bad things. The same applies to other forms of raw I/O > (/dev/mem, /dev/port, ioperm, iopl, etc.) I don't think it makes sense to use the taint flags as a security mechanism. They w

Re: RFC: Tainting the kernel on raw I/O access

2014-09-03 Thread Matthew Garrett
(Cc: Kees) On Wed, Sep 03, 2014 at 02:20:59PM -0700, H. Peter Anvin wrote: > In a meeting earlier today, we discussed MSR access and that it could be > used to do bad things. The same applies to other forms of raw I/O > (/dev/mem, /dev/port, ioperm, iopl, etc.) > > This is basically the same pro

Re: RFC: Tainting the kernel on raw I/O access

2014-09-03 Thread One Thousand Gnomes
On Wed, 03 Sep 2014 14:20:59 -0700 "H. Peter Anvin" wrote: > In a meeting earlier today, we discussed MSR access and that it could be > used to do bad things. The same applies to other forms of raw I/O > (/dev/mem, /dev/port, ioperm, iopl, etc.) For MSR I assume writing primarily - but if you b

Re: RFC: Tainting the kernel on raw I/O access

2014-09-03 Thread H. Peter Anvin
On 09/03/2014 03:20 PM, One Thousand Gnomes wrote: > > If you just want some "detector bits" for bug report filtering them its > quite a different need to fixing "secure" boot mode. Even in the detector > bits case there should be an overall plan and some defined properties > that provide the secu

RFC: Tainting the kernel on raw I/O access

2014-09-03 Thread H. Peter Anvin
In a meeting earlier today, we discussed MSR access and that it could be used to do bad things. The same applies to other forms of raw I/O (/dev/mem, /dev/port, ioperm, iopl, etc.) This is basically the same problem with which the secure boot people have been struggling. Peter Z. suggested we sh