|PKEY_ALLOC(2)||Linux Programmer's Manual||PKEY_ALLOC(2)|
#define _GNU_SOURCE /* See feature_test_macros(7) */ #include <sys/mman.h>
int pkey_alloc(unsigned int flags, unsigned int access_rights); int pkey_free(int pkey);
The pkey_alloc() flags is reserved for future use and currently must always be specified as 0.
The pkey_alloc() access_rights argument may contain zero or more disable operations:
- Disable all data access to memory covered by the returned protection key.
- Disable write access to memory covered by the returned protection key.
pkey_free() frees a protection key and makes it available for later allocations. After a protection key has been freed, it may no longer be used in any protection-key-related operations.
An application should not call pkey_free() on any protection key which has been assigned to an address range by pkey_mprotect(2) and which is still in use. The behavior in this case is undefined and may result in an error.
- pkey, flags, or access_rights is invalid.
- (pkey_alloc()) All protection keys available for the current process have been allocated. The number of keys available is architecture-specific and implementation-specific and may be reduced by kernel-internal use of certain keys. There are currently 15 keys available to user programs on x86.
- This error will also be returned if the processor or operating system does not support protection keys. Applications should always be prepared to handle this error, since factors outside of the application's control can reduce the number of available pkeys.
The kernel guarantees that the contents of the hardware rights register (PKRU) will be preserved only for allocated protection keys. Any time a key is unallocated (either before the first call returning that key from pkey_alloc() or after it is freed via pkey_free()), the kernel may make arbitrary changes to the parts of the rights register affecting access to that key.