This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TLS redux
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>, "GNU C. Library" <libc-alpha at sourceware dot org>
- Cc: Konstantin Serebryany <kcc at google dot com>
- Date: Thu, 23 Jan 2014 10:56:46 -0500
- Subject: Re: TLS redux
- Authentication-results: sourceware.org; auth=none
- References: <20140115022335 dot EB13174430 at topped-with-meat dot com>
On 01/14/2014 09:23 PM, Roland McGrath wrote:
> Similarly, Carlos expressed an attitude that I'll summarize as, "So we
> break ASan for a release or three and fix it later, no big deal."
> That is fundamentally anti-conservative IMHO. Indeed, ASan is not
> part of glibc. If it were, we'd be able to achieve complete
> confidence about all its issues very quickly. ASan is an example of
> the wide variety of things users are doing with glibc, that we have an
> obligation never to break silently or inadvertently.
You get to say "I told you so." and complain again about the
exuberance of naiveté of youth.
I've been working off-list with Kostya to look into the ASan
breakage, helping with internal glibc build and test of
applications against the current glibc master [1].
Kostya has just confirmed that the TLS changes do not break
ASan but do break LeakSanitizer:
https://sourceware.org/bugzilla/show_bug.cgi?id=16291#c14
I still think that fixing correctness issues in TLS is
the right thing to do. Now we get to talk about how we might
fix LeakSanitizer and what information it needs.
Ideas welcome...
Cheers,
Carlos.
[1] https://sourceware.org/glibc/wiki/Testing/Builds