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/14485] File corruption race condition in robust mutex unlocking


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

Torvald Riegel <triegel at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |triegel at redhat dot com
           Assignee|unassigned at sourceware dot org   |triegel at redhat dot com

--- Comment #9 from Torvald Riegel <triegel at redhat dot com> ---
I agree that there is an issue if we claim that a robust mutex can be destroyed
as soon as the thread that wants to destroy it can acquire it and there is no
other thread or process trying to acquire it anymore.  I don't think that
whether we consider destruction or unmap without destruction makes a
significant difference, except regarding performance of potential solutions.

-- 
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]