From: Fangrui Song <i@maskray.me>
To: musl@lists.openwall.com, "Carlos O'Donell" <carlos@redhat.com>
Cc: Eleanor Bartle <eleanor@eleanor-nb.com>,
Markus Wichmann <nullplan@gmx.net>
Subject: Re: [musl] Care about Symbol Namespacing?
Date: Sun, 3 Dec 2023 07:54:45 -0800 [thread overview]
Message-ID: <DS7PR12MB576588D100D66D8801752107CB87A@DS7PR12MB5765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <b3b3aa7d-da8c-80a5-0857-e31756a3a1a6@redhat.com>
On Wed, Nov 29, 2023 at 5:46 AM Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 11/28/23 00:17, Fangrui Song wrote:
> > GNU symbol versioning is actually a system that provides the import
> > file information: vn_file. However, glibc rtld does not utilize
> > vn_file to speed up symbol searches. In addition,
> >
> >> https://maskray.me/blog/2020-11-26-all-about-symbol-versioning#version-script
> >> vn_file is essentially ignored for symbol search since glibc 2.30
> >> https://sourceware.org/bugzilla/show_bug.cgi?id=24741 . Previously
> >> during relocation resolving, after an object failed to provide a
> >> match, if it matched vn_file, rtld would report an error `symbol %s
> >> version %s not defined in file %s with link time reference`.
>
> This change in glibc was intentional.
Yes. I agree that dropping the error is useful for symbol versioning.
> I agree with Rich here that static linking
> should be treated as a first class feature and glibc has moved towards ensuring
> that dynamic and static linking behaviour is more similar.
The similarity between archives and shared objects is a vague concept.
That said, I have tried to figure out the similar parts at
https://maskray.me/blog/2021-05-16-elf-interposition-and-bsymbolic#elf-interposition
* If a dynamic symbol is defined by multiple components, they don't conflict.
* For a symbol lookup (due to a relocation like
R_*_JUMP_SLOT/R_*_GLOB_DAT/absolute relocation/etc), the definition
from the first component wins.
* Definitions from subsequent components are overridden.
We can still add Solaris direct bindings style symbol search while
preserving these properties.
> The exception here is
> that in glibc the goal will be to give developers the option to disallow
> dlopen() from a statically linked application; thus providing the developer
> assurances that nothing else will be loaded (important when crossing namespace
> boundaries, particularly mount namespaces).
>
> --
> Cheers,
> Carlos.
>
prev parent reply other threads:[~2023-12-03 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 2:32 Eleanor Bartle
2023-11-14 3:10 ` Rich Felker
2023-11-14 3:33 ` Eleanor Bartle
2023-11-14 15:35 ` Markus Wichmann
2023-11-15 6:11 ` Eleanor Bartle
2023-11-15 15:20 ` Rich Felker
2023-11-28 5:17 ` Fangrui Song
2023-11-29 13:45 ` Carlos O'Donell
2023-12-03 15:54 ` Fangrui Song [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DS7PR12MB576588D100D66D8801752107CB87A@DS7PR12MB5765.namprd12.prod.outlook.com \
--to=i@maskray.me \
--cc=carlos@redhat.com \
--cc=eleanor@eleanor-nb.com \
--cc=musl@lists.openwall.com \
--cc=nullplan@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).