[Bug nptl/26964] pthread_mutex_timedlock returning EAGAIN after futex is locked

["tuliom at ascii dot art.br" <sourceware-bugzilla@sourceware.org>]

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

Tulio Magno Quites Machado Filho <tuliom at ascii dot art.br> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |2.33
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #1 from Tulio Magno Quites Machado Filho <tuliom at ascii dot art.br> ---
Fixed with:

commit 61855081017dff30c577855cda882740356b5d98
Author: Lucas A. M. Magalhaes <lamm@linux.ibm.com>
Date:   Tue Dec 1 18:05:07 2020 -0300

    nptl: Fix __futex_clocklock64 return error check [BZ #26964]

    The earlier implementation of this, __lll_clocklock, calls lll_clockwait
    that doesn't return the futex syscall error codes.  It always tries again
    if that fails.

    However in the current implementation, when the futex returns EAGAIN,
    __futex_clocklock64 will also return EGAIN, even if the futex is taken.

    This patch fixes the EAGAIN issue and also adds a check for EINTR.  As
    futex syscall can return EINTR if the thread is interrupted by a signal.
    In this case I'm assuming the function should continue trying to lock as
    there is no mention to about it on POSIX.  Also add a test for both
    scenarios.

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