From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu via Binutils" <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 9/9] ld: Add glibc dependency for DT_RELR
Date: Mon, 10 Jan 2022 07:40:06 -0800 [thread overview]
Message-ID: <CAMe9rOpt2E16Eex456fKJxG0QrWKWQdYGea1ppEot8dsk-e_iA@mail.gmail.com> (raw)
In-Reply-To: <87sftvwqtj.fsf@oldenburg.str.redhat.com>
On Mon, Jan 10, 2022 at 7:31 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu via Binutils:
>
> > + const char *relr = "GLIBC_ABI_DT_RELR";
>
> This needs to be in the implementation namespace, otherwise the user can
> provide their own symbol, effectively breaking the lockout.
>
Isn't "GLIBC_XXX" in the implementation namespace? If not,
can you recommend a name?
Thanks.
--
H.J.
next prev parent reply other threads:[~2022-01-10 15:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 18:38 [PATCH v2 0/9] ld: Implement DT_RELR for x86 H.J. Lu
2022-01-08 18:38 ` [PATCH v2 1/9] elf: Add .relr.dyn to special_sections_r H.J. Lu
2022-01-08 18:38 ` [PATCH v2 2/9] elf: Extract _bfd_elf_process_reverse_copy H.J. Lu
2022-01-08 18:38 ` [PATCH v2 3/9] elf: Pass need_layout to _bfd_elf_map_sections_to_segments H.J. Lu
2022-01-08 18:38 ` [PATCH v2 4/9] ld: Initial DT_RELR support H.J. Lu
2022-01-08 18:38 ` [PATCH v2 5/9] elf: Add size_relative_relocs and finish_relative_relocs H.J. Lu
2022-01-08 18:38 ` [PATCH v2 6/9] elf: Support DT_RELR in linker tests H.J. Lu
2022-01-08 18:38 ` [PATCH v2 7/9] x86: Add DT_RELR support H.J. Lu
2022-01-08 18:38 ` [PATCH v2 8/9] ld: Add simple DT_RELR tests H.J. Lu
2022-01-08 18:38 ` [PATCH v2 9/9] ld: Add glibc dependency for DT_RELR H.J. Lu
2022-01-10 15:31 ` Florian Weimer
2022-01-10 15:40 ` H.J. Lu [this message]
2022-01-10 15:42 ` Florian Weimer
2022-01-08 21:53 ` [PATCH v2 0/9] ld: Implement DT_RELR for x86 Fangrui Song
2022-01-09 8:13 ` Alexander Monakov
2022-01-13 2:54 ` Fangrui Song
2022-01-13 3:00 ` H.J. Lu
2022-01-11 10:13 ` Nick Clifton
2022-01-11 14:08 ` H.J. Lu
2022-01-12 12:33 ` Nick Clifton
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=CAMe9rOpt2E16Eex456fKJxG0QrWKWQdYGea1ppEot8dsk-e_iA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).