| commit | 8d42bf859a289944749d9f978c076cd318119867 | |
| author | Lucas A. M. Magalhaes <lamm@linux.ibm.com> | |
| Mon, 17 Feb 2020 12:09:52 +0000 (17 09:09 -0300) | ||
| committer | Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com> | |
| Wed, 19 Feb 2020 13:54:02 +0000 (19 10:54 -0300) | ||
| tree | 0fec7ff828f19750fcbdefecf5211348a9e519f9 | treesnapshot (tar.gz zip) |
| parent | 7455b700279ec8baccf8dd7b119648f8b3e34eec | commitdiff |
Fix tst-pkey expectations on pkey_get [BZ #23202]
From the GNU C Library manual, the pkey_set can receive a combination of
PKEY_DISABLE_WRITE and PKEY_DISABLE_ACCESS. However PKEY_DISABLE_ACCESS
is more restrictive than PKEY_DISABLE_WRITE and includes its behavior.
The test expects that after setting
(PKEY_DISABLE_WRITE|PKEY_DISABLE_ACCESS) pkey_get should return the
same. This may not be true as PKEY_DISABLE_ACCESS will succeed in
describing the state of the key in this case.
The pkey behavior during signal handling is different between x86 and
POWER. This change make the test compatible with both architectures.
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
From the GNU C Library manual, the pkey_set can receive a combination of
PKEY_DISABLE_WRITE and PKEY_DISABLE_ACCESS. However PKEY_DISABLE_ACCESS
is more restrictive than PKEY_DISABLE_WRITE and includes its behavior.
The test expects that after setting
(PKEY_DISABLE_WRITE|PKEY_DISABLE_ACCESS) pkey_get should return the
same. This may not be true as PKEY_DISABLE_ACCESS will succeed in
describing the state of the key in this case.
The pkey behavior during signal handling is different between x86 and
POWER. This change make the test compatible with both architectures.
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
| sysdeps/unix/sysv/linux/tst-pkey.c | diffblobblamehistory |