diff options
| author | Lucas A. M. Magalhaes <lamm@linux.ibm.com> | 2020-01-16 10:39:12 -0300 |
|---|---|---|
| committer | Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com> | 2020-01-17 09:05:03 -0300 |
| commit | 70ba28f7ab2923d4e36ffc9d5d2e32357353b25c (patch) | |
| tree | a372da0bc6f7aefadc7b069e40a577e923c1034a /benchtests | |
| parent | 18363b4f010da9ba459b13310b113ac0647c2fcc (diff) | |
| download | glibc-70ba28f7ab2923d4e36ffc9d5d2e32357353b25c.tar glibc-70ba28f7ab2923d4e36ffc9d5d2e32357353b25c.tar.gz glibc-70ba28f7ab2923d4e36ffc9d5d2e32357353b25c.tar.bz2 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 'benchtests')
0 files changed, 0 insertions, 0 deletions