lkml.org 
[lkml]   [2018]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/1 v2] x86: pkey-mprotect must allow pkey-0
On Wed, Mar 14, 2018 at 07:19:23AM -0700, Dave Hansen wrote:
> On 03/14/2018 12:46 AM, Ram Pai wrote:
> > Once an address range is associated with an allocated pkey, it cannot be
> > reverted back to key-0. There is no valid reason for the above behavior. On
> > the contrary applications need the ability to do so.
>
> I'm trying to remember why we cared in the first place. :)
>
> Could you add that to the changelog, please?
>
> > @@ -92,7 +92,8 @@ int mm_pkey_alloc(struct mm_struct *mm)
> > static inline
> > int mm_pkey_free(struct mm_struct *mm, int pkey)
> > {
> > - if (!mm_pkey_is_allocated(mm, pkey))
> > + /* pkey 0 is special and can never be freed */
> > + if (!pkey || !mm_pkey_is_allocated(mm, pkey))
> > return -EINVAL;
>
> If an app was being really careful, couldn't it free up all of the
> implicitly-pkey-0-assigned memory so that it is not in use at all? In
> that case, we might want to allow this.
>
> On the other hand, nobody is likely to _ever_ actually do this so this
> is good shoot-yourself-in-the-foot protection.

I look at key-0 as 'the key'. It has special status.
(a) It always exist.
(b) it cannot be freed.
(c) it is assigned by default.
(d) its permissions cannot be modified.
(e) it bypasses key-permission checks when assigned.

An arch need not necessarily map 'the key-0' to its key-0. It could
internally map it to any of its internal key of its choice, transparent
to the application.

Do you see a problem to this view point?

RP

\
 
 \ /
  Last update: 2018-03-14 18:15    [W:0.045 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site