about summary refs log tree commit diff
path: root/manual
diff options
context:
space:
mode:
authorLucas A. M. Magalhaes <lamm@linux.ibm.com>2020-01-16 10:39:12 -0300
committerTulio Magno Quites Machado Filho <tuliom@linux.ibm.com>2020-01-17 09:05:03 -0300
commit70ba28f7ab2923d4e36ffc9d5d2e32357353b25c (patch)
treea372da0bc6f7aefadc7b069e40a577e923c1034a /manual
parent18363b4f010da9ba459b13310b113ac0647c2fcc (diff)
downloadglibc-70ba28f7ab2923d4e36ffc9d5d2e32357353b25c.tar.gz
glibc-70ba28f7ab2923d4e36ffc9d5d2e32357353b25c.tar.xz
glibc-70ba28f7ab2923d4e36ffc9d5d2e32357353b25c.zip
Fix tst-pkey.c pkey_alloc return checks and manual
This test was failing in some powerpc systems as it was not checking
for ENOSPC return.

As said on the Linux man-pages and can be observed by the implementation
at mm/mprotect.c in the Linux Kernel source.  The syscall pkey_alloc can
return EINVAL or ENOSPC.  ENOSPC will indicate either that all keys are
in use or that the kernel does not support pkeys.

Reviewed-by: Gabriel F. T. Gomes <gabriel@inconstante.net.br>
Diffstat (limited to 'manual')
-rw-r--r--manual/memory.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/manual/memory.texi b/manual/memory.texi
index b565dd69f2..aa5011e4f9 100644
--- a/manual/memory.texi
+++ b/manual/memory.texi
@@ -3288,6 +3288,10 @@ in which memory protection keys are disabled.
 
 @item ENOSPC
 All available protection keys already have been allocated.
+
+The system does not implement memory protection keys or runs in a mode
+in which memory protection keys are disabled.
+
 @end table
 @end deftypefun