[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1656e926-f277-710e-71ad-1ff2fe77886b@intel.com>
Date: Tue, 16 May 2023 15:30:50 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Jeff Xu <jeffxu@...gle.com>, Kees Cook <keescook@...omium.org>
Cc: jeffxu@...omium.org, luto@...nel.org, jorgelo@...omium.org,
groeck@...omium.org, jannh@...gle.com, sroettger@...gle.com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-mm@...ck.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH 0/6] Memory Mapping (VMA) protection using PKU - set 1
On 5/16/23 15:17, Jeff Xu wrote:
>>> This set of patch covers mprotect/munmap, I plan to work on other
>>> syscalls after this.
>> Which ones are on your list currently?
>>
> mprotect/mprotect_pkey/munmap
> mmap/mremap
> madvice,brk,sbrk
What about pkey_free()?
Without that, someone can presumably free the pkey and then reallocate
it without PKEY_ENFORCE_API.
Powered by blists - more mailing lists