Thread (16 messages) flat view 16 messages, 6 authors, 2018-03-14

Re: [PATCH] x86, powerpc : pkey-mprotect must allow pkey-0

From: Dave Hansen <hidden>
Date: 2018-03-10 06:50:38
Also in: linux-arch, linux-mm, lkml

On 03/09/2018 09:55 PM, Ram Pai wrote:
On Fri, Mar 09, 2018 at 02:40:32PM -0800, Dave Hansen wrote:
quoted
On 03/09/2018 12:12 AM, Ram Pai wrote:
quoted
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.
Why don't we just set pkey 0 to be allocated in the allocation bitmap by
default?
ok. that will make it allocatable. But it will not be associatable,
given the bug in the current code. And what will be the
default key associated with a pte? zero? or something else?
I'm just saying that I think we should try to keep from making it
special as much as possible.

Let's fix the bug that keeps it from being associatable.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help