This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Async signal safe TLS accesses
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Rich Felker <dalias at aerifal dot cx>, Alexandre Oliva <aoliva at redhat dot com>
- Cc: Paul Pluzhnikov <ppluzhnikov at google dot com>, Andrew Hunter <ahh at google dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Mon, 02 Dec 2013 16:58:52 -0500
- Subject: Re: [PATCH] Async signal safe TLS accesses
- Authentication-results: sourceware.org; auth=none
- References: <CALoOobMsO6X86JFD4J7F-EL-J+xOTEOVbzH=6mwrvfCnFvw57Q at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1311052233090 dot 30260 at digraph dot polyomino dot org dot uk> <CALoOobM70-mix+=1zuDnSoK7SRqQChbL=03xBkUcFf1fyS1Mjw at mail dot gmail dot com> <CALoOobP7kdpZCZA0a7MZWCtONu81fW4H_qAWOEfpfvzxJgG_=Q at mail dot gmail dot com> <CALoOobP6rTDosadvLKhHY+deDsU-FtvyO8QX_Y4dZy716e2ATQ at mail dot gmail dot com> <CALoOobOCT-inwMZkzEr+JYT4c8qwpN-EGMPFu_kHQTpc2icj0g at mail dot gmail dot com> <CALoOobPHo7+jG0nfiZp9afC2rArLUMRYZEag21W+78UBTZF=CQ at mail dot gmail dot com> <orvbzckoif dot fsf at livre dot home> <20131129015405 dot GY24286 at brightrain dot aerifal dot cx> <ortxetkccq dot fsf at livre dot home> <20131130183236 dot GU24286 at brightrain dot aerifal dot cx>
On 11/30/2013 01:32 PM, Rich Felker wrote:
> I'm against any attempt to make anything "safe" under async
> cancellation. Calling any library functions at all (other than to
> disable async cancellation) with async cancellation active is just a
> serious programming error. There are way too many things that can go
> wrong, and no good reason to do it.
I think we should make pthread_testcancel AS-Safe and guarantee that
in glibc to fix the POSIX design flaw and then file a bug with the
Austin group to have it on record (even if its promptly closed).
There are some cases where AS-Safety is useful, and I'd like to see
that small bubble extended just a little bit.
This is however an entirely different topic form the one at hand,
but since I saw your comment about pthread_testcancel, I wanted to
put the bug in your ear.