This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/14485] File corruption race condition in robust mutex unlocking
- From: "triegel at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 10 Feb 2015 21:57:01 +0000
- Subject: [Bug nptl/14485] File corruption race condition in robust mutex unlocking
- Auto-submitted: auto-generated
- References: <bug-14485-131 at http dot sourceware dot org/bugzilla/>
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.