From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Bruno Haible <bruno@clisp.org>
Cc: libc-alpha@sourceware.org, bug-gnulib@gnu.org, binutils@sourceware.org
Subject: Re: Undefined use of weak symbols in gnulib
Date: Wed, 28 Apr 2021 19:43:39 +0200 [thread overview]
Message-ID: <87sg3agv90.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <2800926.834q8TerIH@omega> (Bruno Haible's message of "Wed, 28 Apr 2021 16:40:18 +0200")
* Bruno Haible:
> So, in the normal cases (link with '-lpthread', link without '-lpthread',
> and even with dlopen()), everything will work fine. The only problematic
> case thus is the the use of LD_PRELOAD. Right?
LD_PRELOAD and glibc 2.34 as originally planned.
> I think few packages in a distro will be affected. And few users are
> using LD_PRELOAD on their own, because since the time when glibc
> started to use 'internal' calls to system calls where possible, there
> are not a lot of uses of LD_PRELOAD that still work.
We get the occasional bug report when these things break. We have not
seen much of that yet because our gnulib-using programs are still at
older versions for most of our users.
Here's an example of such a bug report, although not for libpthread:
powerpc: libc segfaults when LD_PRELOADed with libgcc
<https://sourceware.org/bugzilla/show_bug.cgi?id=26615>
I think in this bug, libc.so.6 was invoked during some build process
(which could easily run bison as well, so it has to work with
LD_PRELOAD).
>> No. glibc 2.34 will behave as if an implicit -lpthread is present on
>> the linker program line.
>
> Good. This means a bullet-proof way for a distro to avoid the problem
> is to "rebuild the world" after importing glibc 2.34.
Yeah, but that's not good enough. So I spent today on coming up with a
workaround in glibc.
>> No, it's unrelated. The crash or other undefined behavior is a
>> consequence of actions of the link editor and cannot be reverted at run
>> time.
>
> In other words, the problem is that
> - there are some/many binaries out there, that were produced by an 'ld'
> that did not anticipate the changes in glibc 2.34, and
> - these binaries have a problem not when run directly, but only when
> run with LD_PRELOAD.
>
> Right?
No, glibc 2.34 won't need LD_PRELOAD to expose the bug. LD_PRELOAD is
just a development aid that reveals the problem with glibc 2.33 and
earlier.
Thanks,
Florian
next prev parent reply other threads:[~2021-04-28 17:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 5:53 Undefined use of weak symbols in gnulib Florian Weimer via Libc-alpha
2021-04-27 6:50 ` Paul Eggert
2021-04-27 6:58 ` Florian Weimer via Libc-alpha
2021-04-27 7:13 ` Paul Eggert
2021-04-27 7:24 ` Andreas Schwab
2021-04-27 11:06 ` Florian Weimer via Libc-alpha
2021-04-28 0:09 ` Bruno Haible
2021-04-28 2:10 ` H.J. Lu via Libc-alpha
2021-04-28 2:13 ` H.J. Lu via Libc-alpha
2021-05-05 20:31 ` Fangrui Song
2021-04-28 8:35 ` Florian Weimer via Libc-alpha
2021-04-28 13:15 ` Michael Matz
2021-04-28 7:44 ` Florian Weimer via Libc-alpha
2021-04-28 14:48 ` Bruno Haible
2021-04-28 17:44 ` Florian Weimer via Libc-alpha
2021-07-17 14:38 ` Bruno Haible
2021-07-17 14:55 ` Florian Weimer via Libc-alpha
2021-07-17 16:39 ` Bruno Haible
2021-07-27 20:02 ` Joseph Myers
2021-07-27 20:19 ` Florian Weimer via Libc-alpha
2021-07-27 23:38 ` Paul Eggert
2021-04-27 23:22 ` Bruno Haible
2021-04-27 23:47 ` Bruno Haible
2021-04-28 7:57 ` Florian Weimer via Libc-alpha
2021-04-28 14:40 ` Bruno Haible
2021-04-28 17:43 ` Florian Weimer via Libc-alpha [this message]
2021-04-29 15:15 ` Bruno Haible
2021-04-30 9:55 ` Florian Weimer via Libc-alpha
2021-04-29 6:33 ` Ben Pfaff via Libc-alpha
2021-05-03 1:44 ` Alan Modra via Libc-alpha
2021-07-12 10:04 ` Michael Hudson-Doyle via Libc-alpha
2021-07-12 15:03 ` Florian Weimer via Libc-alpha
2021-07-12 15:30 ` Matthias Klose
2021-07-12 15:37 ` Florian Weimer via Libc-alpha
2021-07-13 0:22 ` Michael Hudson-Doyle via Libc-alpha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg3agv90.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=binutils@sourceware.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=fweimer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).