Re: [PATCH 1/2] x86/pkeys: copy pkey state at fork()

From: Dave Hansen
Date: Fri Oct 26 2018 - 16:00:01 EST

Next message: Mikulas Patocka: "Re: [dm-devel] [RFC] dm-bow working prototype"
Previous message: Dave Hansen: "[PATCH 2/2] x86/selftests/pkeys: fork() to check for state being preserved"
In reply to: Dave Hansen: "[PATCH 2/2] x86/selftests/pkeys: fork() to check for state being preserved"
Next in thread: Daniel Micay: "Re: [PATCH 1/2] x86/pkeys: copy pkey state at fork()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 10/26/18 12:51 PM, Dave Hansen wrote:
...
> The result is that, after a fork(), the child's pkey state ends up
> looking like it does after an execve(), which is totally wrong. pkeys
> that are already allocated can be allocated again, for instance.

One thing I omitted. This was very nicely discovered and reported by
danielmicay@xxxxxxxxxx Thanks, Daniel!

Next message: Mikulas Patocka: "Re: [dm-devel] [RFC] dm-bow working prototype"
Previous message: Dave Hansen: "[PATCH 2/2] x86/selftests/pkeys: fork() to check for state being preserved"
In reply to: Dave Hansen: "[PATCH 2/2] x86/selftests/pkeys: fork() to check for state being preserved"
Next in thread: Daniel Micay: "Re: [PATCH 1/2] x86/pkeys: copy pkey state at fork()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]