Re: [PATCH] mtrr: s/suser/capable/

From: Tigran Aivazian (tigran@veritas.com)
Date: Thu Aug 31 2000 - 07:41:09 EDT

Next message: Ingo Molnar: "Re: Reserving a (large) memory block"

Previous message: Matthew Kirkwood: "Re: [PATCH] mtrr: s/suser/capable/"
In reply to: Andi Kleen: "Re: [PATCH] mtrr: s/suser/capable/"
Next in thread: Alan Cox: "Re: [PATCH] mtrr: s/suser/capable/"
Next in thread: Andi Kleen: "Re: [PATCH] mtrr: s/suser/capable/"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 31 Aug 2000, Andi Kleen wrote:

> On Thu, Aug 31, 2000 at 12:11:31PM +0100, Alan Cox wrote:
> > > > These cases in mtrr.c are clearly CAP_SYS_RAWIO.
> > >
> > > Clearly? How do MTRR changes relate to rawio ?
> >
> > RAWIO is about hardware level access not Stephens O_DIRECT stuff
>
> So why is /proc/kcore access SYS_RAWIO then ?

because via /proc/kcore you can access hardware (with Kanoj's recent patch
i.e.)

>
> And why is nvram access not SYS_RAWIO ?

because it's a bug. I see it uses CAP_SYS_ADMIN but it should really use
CAP_SYS_RAWIO.

Regards,
Tigran

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

Next message: Ingo Molnar: "Re: Reserving a (large) memory block"
Previous message: Matthew Kirkwood: "Re: [PATCH] mtrr: s/suser/capable/"
In reply to: Andi Kleen: "Re: [PATCH] mtrr: s/suser/capable/"
Next in thread: Alan Cox: "Re: [PATCH] mtrr: s/suser/capable/"
Next in thread: Andi Kleen: "Re: [PATCH] mtrr: s/suser/capable/"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 07:53:32 EDT