This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] mutex destruction (#13690): problem description and workarounds
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: Rich Felker <dalias at libc dot org>, GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Thu, 04 Dec 2014 10:16:03 -0500
- Subject: Re: [RFC] mutex destruction (#13690): problem description and workarounds
- Authentication-results: sourceware.org; auth=none
- References: <1396621230 dot 10643 dot 7191 dot camel at triegel dot csb> <20141201153802 dot GV29621 at brightrain dot aerifal dot cx> <1417452125 dot 1771 dot 503 dot camel at triegel dot csb> <20141201170542 dot GY29621 at brightrain dot aerifal dot cx> <1417467150 dot 1771 dot 581 dot camel at triegel dot csb> <20141201212223 dot GZ29621 at brightrain dot aerifal dot cx> <1417553118 dot 3930 dot 14 dot camel at triegel dot csb> <547F1734 dot 40903 at redhat dot com> <1417704117 dot 22797 dot 23 dot camel at triegel dot csb>
On 12/04/2014 09:41 AM, Torvald Riegel wrote:
> On Wed, 2014-12-03 at 08:59 -0500, Carlos O'Donell wrote:
>> I don't quite follow what you're trying to argue. Could you expand in
>> another thread with code examples?
>
> The underlying issues has been discussed in this thread. For EINTR on
> futex_wait specifically, spurious wake-ups is something documented by
> the kernel already.
>
> I have put comments in the code of my semaphore patch that explains how
> it relates to semaphores and their rules around EINTR.
Thanks.
Cheers,
Carlos.