[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <FF299375-B46F-46D0-90A9-333959FE9380@gmail.com>
Date: Thu, 7 Sep 2023 17:22:10 -0400
From: Robert Kueffner <r.m.kueffner@...il.com>
To: Kyle Huey <me@...ehuey.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Robert Kueffner <r.m.kueffner@...il.com>
Subject: Memory protection keys: Signal handlers crash if pkey0 is
write-disabled
I am trying to establish memory protection domains in x86/linux using memory protection keys and the protection key register PKRU.
Briefly:
(1) My program allocates a new protection key pkey1 and associated memory, and installs custom signal handlers for FPE+SEGV
(2) I define "user code" as code that should only operate in that memory, i.e. I want to disable write on pages with pkey0 by setting PKRU.WD0=true
(3) In this setup, if the user code causes an exception, the kernel causes an additional SEGV when switching to my signal handler
(a) in case of user code causing SEGV this occurs upon return from sigprocmask()
(b) in case of user code causing FPE this occurs right upon switching to the signal handler
(3) only happens when user code runs with WD0=true, my example code tests successfully as long as WD0=false
Is there some way to make this work, or is it generally not possible to successfully handle exceptions if WD0=true?
More details and a minimal implementation: https://unix.stackexchange.com/questions/755160/memory-protection-keys-exception-handler-crashes-if-pkey0-is-write-disabled
Robert
---
12th Gen Intel(R) Core(TM) i7-12700
Linux version 6.2.0-32-generic (buildd@...02-amd64-023) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #32-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 14 10:03:50 UTC 2023
Powered by blists - more mailing lists