Re: [PATCH 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: jeffxu@xxxxxxxxxxxx
Subject: Re: [PATCH 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect
From: Kees Cook <keescook@xxxxxxxxxxxx>
Date: Tue, 16 May 2023 13:07:39 -0700
Cc: dave.hansen@xxxxxxxxx, luto@xxxxxxxxxx, jorgelo@xxxxxxxxxxxx, groeck@xxxxxxxxxxxx, jannh@xxxxxxxxxx, sroettger@xxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, jeffxu@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-kselftest@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-hardening@xxxxxxxxxxxxxxx
In-reply-to: <20230515130553.2311248-4-jeffxu@chromium.org>
References: <20230515130553.2311248-1-jeffxu@chromium.org> <20230515130553.2311248-4-jeffxu@chromium.org>

On Mon, May 15, 2023 at 01:05:49PM +0000, jeffxu@xxxxxxxxxxxx wrote:
> From: Jeff Xu <jeffxu@xxxxxxxxxx>
> 
> This patch enables PKEY_ENFORCE_API for the mprotect and
> mprotect_pkey syscalls.

All callers are from userspace -- this change looks like a no-op?

-Kees

-- 
Kees Cook

Follow-Ups:
- Re: [PATCH 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect
  - From: Jeff Xu

References:
- [PATCH 0/6] Memory Mapping (VMA) protection using PKU - set 1
  - From: jeffxu
- [PATCH 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect
  - From: jeffxu

Prev by Date: Re: [PATCH 5/6] KEY: Apply PKEY_ENFORCE_API to munmap
Next by Date: Re: [PATCH 0/6] Memory Mapping (VMA) protection using PKU - set 1
Previous by thread: [PATCH 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect
Next by thread: Re: [PATCH 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux