[Bug libc/23202] tst-pkeys fails on POWER

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=23202

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tulio Magno Quites Machado Filho
<tuliom@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8d42bf859a289944749d9f978c076cd318119867

commit 8d42bf859a289944749d9f978c076cd318119867
Author: Lucas A. M. Magalhaes <lamm@linux.ibm.com>
Date:   Mon Feb 17 09:09:52 2020 -0300

    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>

-- 
You are receiving this mail because:
You are on the CC list for the bug.