This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nptl/20263] robust mutex deadlocks if other thread requests timedlock (Only arm/linux)


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

Jiyoung Yun <t2wish at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t2wish at gmail dot com

--- Comment #6 from Jiyoung Yun <t2wish at gmail dot com> ---
Created attachment 9365
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9365&action=edit
Robust mutex timed out test code

In Linux/ARM environment, a robust mutex can't catch the timeout result
when it is already owned by other thread and requests to try lock with
a specific time value(pthread_mutex_timedlock). The futex already returns
the ETIMEDOUT result but there is no check the return value and it makes
a deadlock.

* nptl/lowlevelrobustlock.c: Implement ETIMEDOUT logic.

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]