linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
	linux-api@vger.kernel.org, linux-mm@kvack.org
Subject: Re: pkeys: Reserve PKEY_DISABLE_READ
Date: Thu, 08 Nov 2018 21:14:19 +0100	[thread overview]
Message-ID: <87ftwb72ec.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20181108200859.GD5481@ram.oc3035372033.ibm.com> (Ram Pai's message of "Thu, 8 Nov 2018 12:08:59 -0800")

* Ram Pai:

> Hi Dave! :) So what is needed? Support a new flag PKEY_DISABLE_READ,
> and make it return error for all architectures?

PKEY_DISABLE_READ | PKEY_DISABLE_WRITE should be equivalent to
PKEY_DISABLE_ACCESS.  PKEY_DISABLE_READ without any other flag on x86
should return EINVAL (as for other invalid access rights specified for
pkey_alloc).

> Or are we enhancing the symantics of pkey_alloc() to allocate keys with
> just disable-read permissions.? And if so, will x86 be able to support
> that semantics?

I think x86 cannot do this, but POWER can, but it's currently not
possible to express this via pkey_alloc.  That could be fixed, too.

Thanks,
Florian

  parent reply	other threads:[~2018-11-08 20:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 12:05 pkeys: Reserve PKEY_DISABLE_READ Florian Weimer
2018-11-08 14:57 ` Dave Hansen
2018-11-08 15:01   ` Florian Weimer
2018-11-08 17:14     ` Dave Hansen
2018-11-08 17:37       ` Florian Weimer
2018-11-08 20:12         ` Ram Pai
2018-11-08 20:23           ` Florian Weimer
2018-11-09 18:09             ` Ram Pai
2018-11-12 12:00               ` Florian Weimer
2018-11-27 10:23                 ` Ram Pai
2018-11-27 11:57                   ` Florian Weimer
2018-11-27 15:31                     ` Dave Hansen
2018-11-29 11:37                       ` Florian Weimer
2018-12-03  4:02                         ` Ram Pai
2018-12-03 15:52                           ` Florian Weimer
2018-12-04  6:23                             ` Ram Pai
2018-12-05 13:00                               ` Florian Weimer
2018-12-05 20:23                                 ` Ram Pai
2018-12-05 16:21                           ` Andy Lutomirski
2018-12-05 20:36                             ` Ram Pai
2018-11-08 20:08       ` Ram Pai
2018-11-08 20:11         ` Dave Hansen
2018-11-08 20:14         ` Florian Weimer [this message]
2018-11-08 19:22 ` Ram Pai
2018-11-12 10:29   ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftwb72ec.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dave.hansen@intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxram@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).