From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH] Add GLIBC_PRIVATE_RELR as proxy for DT_RELR
Date: Fri, 19 Nov 2021 07:36:57 -0800 [thread overview]
Message-ID: <CAMe9rOo3zj6GtMwdwDCBU4DBiU1-MLXitGM=8oF4eC28UVOwAw@mail.gmail.com> (raw)
In-Reply-To: <87zgq0b1t4.fsf@oldenburg.str.redhat.com>
On Fri, Nov 19, 2021 at 7:30 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> > Executables with DT_RELR will crash mysteriously with glibc binaries
> > without DT_RELR support. Bump EI_ABIVERSION won't prevent crash since
> > the Linux kernel loader doesn't check EI_ABIVERSION on executables.
> > Adding a glibc version dependency on the first glibc version with
> > DT_RELR support will prevent backporting DT_RELR support to released
> > glibc branches.
> >
> > Add a GLIBC_PRIVATE_RELR version as a proxy for DT_RELR support in glibc.
> > Linker should add the GLIBC_PRIVATE_RELR version dependency on binaries
> > with DT_RELR. GLIBC_PRIVATE_RELR should be backported together when
> > backporting DT_RELR support.
>
> I don't like it. What's wrong about EI_ABIVERSION?
Bumping EI_ABIVERSION on executables doesn't prevent crashes
with existing ld.so binaries.
> The kernel doesn't need to check EI_ABIVERSION because it does not do
> relocation processing.
>
> Thanks,
> Florian
>
--
H.J.
next prev parent reply other threads:[~2021-11-19 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 15:26 H.J. Lu
2021-11-19 15:30 ` Florian Weimer
2021-11-19 15:36 ` H.J. Lu [this message]
2021-11-19 22:47 ` Florian Weimer
2021-11-20 2:55 ` H.J. Lu
2021-11-22 18:21 ` Joseph Myers
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='CAMe9rOo3zj6GtMwdwDCBU4DBiU1-MLXitGM=8oF4eC28UVOwAw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.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).