This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Async signal safe TLS accesses
- From: Ian Lance Taylor <iant at google dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, Rich Felker <dalias at aerifal dot cx>, Andrew Hunter <ahh at google dot com>, GNU C Library <libc-alpha at sourceware dot org>, Paul Pluzhnikov <ppluzhnikov at google dot com>
- Date: Wed, 2 Oct 2013 15:17:43 -0700
- Subject: Re: [PATCH] Async signal safe TLS accesses
- Authentication-results: sourceware.org; auth=none
- References: <523F2ED8 dot 8090909 at redhat dot com> <1379977289-21260-1-git-send-email-ahh at google dot com> <20130924025738 dot GK20515 at brightrain dot aerifal dot cx> <524C3467 dot 2030503 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1310022203420 dot 22120 at digraph dot polyomino dot org dot uk>
On Wed, Oct 2, 2013 at 3:08 PM, Joseph S. Myers <email@example.com> wrote:
> I do think there is consensus for allowing TLS access in signal handlers.
> I'd like there to be consensus for TLS accesses never failing (i.e. all
> dynamic allocation being done at thread creation time or dlopen time, when
> it's possible to return an error status, and initial accesses doing no
> more than associating a variable with memory from a pool where a
> sufficient amount of memory is guaranteed to have been allocated at one of
> those times), but while I don't think anyone has objected to that, I'm not
> sure enough people have actually thought about it.
I agree, but for some initial thoughts see