This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.19 - asyn-signal safe TLS and ASan.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Kostya Serebryany <kcc at google dot com>, Paul Pluzhnikov <ppluzhnikov at google dot com>
- Cc: OndÅej BÃlka <neleai at seznam dot cz>, "Joseph S. Myers" <joseph at codesourcery dot com>, Andrew Hunter <ahh at google dot com>, GNU C Library <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>, address-sanitizer at googlegroups dot com
- Date: Thu, 30 Jan 2014 00:23:51 -0500
- Subject: Re: glibc 2.19 - asyn-signal safe TLS and ASan.
- Authentication-results: sourceware.org; auth=none
- References: <52D0BCED dot 3000109 at redhat dot com> <52DDBF0E dot 8010501 at redhat dot com> <CAN=P9piS3Xczq2AKrzh4rsK9JxiHtJXawcQs9_+xsYXxrbLQWQ at mail dot gmail dot com> <CADroS=6vODmWCdBsynOf7oM9uVDymwdxrSDFbmD6kT5P9gbBRw at mail dot gmail dot com> <CAN=P9pgAYNZBUBbg2_SiwCjB5vXJ6ZXTNS=yoZWSvS3JoX1bGQ at mail dot gmail dot com> <52E2A098 dot 7060908 at google dot com> <Pine dot LNX dot 4 dot 64 dot 1401241747120 dot 9799 at digraph dot polyomino dot org dot uk> <CAN=P9pio-MWtJ=F4MmjA5_NJexv1nC12tR=Ue7iD3uq-ootG+w at mail dot gmail dot com> <20140125010534 dot GA14587 at domone dot podge> <CALoOobNc8mNUHLhry-hcqT6fx9m=HukMw1Sy41Q+uhRDBznbSw at mail dot gmail dot com> <20140125030232 dot GA14213 at domone dot podge> <CAN=P9pgiMRxxYK16ZaVje1AQbC+fQ=QUDhsdww5-8RWaiJswoA at mail dot gmail dot com> <CALoOobMdh7wOHPPB6vTTLb0wXeO-yGA75MvHohrqGPAY-CcC2g at mail dot gmail dot com> <CAN=P9pjAW6bMip+hsE6mDUA2MFfdC7fNCvrgNyhG2GRQGJJNCw at mail dot gmail dot com> <CAN=P9pj+EVcrUwxa+70eEVY-_sqaU1d6s8HjsP4BkY8N+G-JVg at mail dot gmail dot com>
On 01/29/2014 04:48 AM, Kostya Serebryany wrote:
> [text only]
>
>> Indeed so, thanks!
>> So, exporting __signal_safe_memalign&co will allow us to extend the
>> existing hack to 2.19.
>> If this simple change can not be done for 2.19, can *anything* be done at all?
>> (Long term we'd still prefer something less hackish)
>
> FTR, I've implemented an even-uglier-then-before hack that deals with
> dynamic TLS in both <=2.18 and 2.19.
> So, we will survive the 2.19 release.
> But I would appreciate if we can resolve
> https://sourceware.org/bugzilla/show_bug.cgi?id=16291
> before the next one (2.20).
Can you please describe the hack?
Cheers,
Carlos.