From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 0/3] Remove prelink support
Date: Mon, 24 Jan 2022 15:55:59 -0300 [thread overview]
Message-ID: <9ac94bc2-a7aa-decf-290f-c995a156c058@linaro.org> (raw)
In-Reply-To: <20220121172951.285848-1-adhemerval.zanella@linaro.org>
On 21/01/2022 14:29, Adhemerval Zanella wrote:
> As discussed recently on maillist [1], prelink is deprecated in
> practice:
>
> * There is no active development neither maintainace.
> * It misses supports for some architectures, even for architecture
> wildly deployed such as aarch64 [2].
> * It does not work with recent security hardening such as PIE.
> * Nor it will work on future ABI additions such as DT_RELR.
> * Even when PIE is not enabled its coverity if flacky, with some
> binaries showing corrupted state [3].
> * Recent glibc changes to support different tools (such as lld)
> showed inherent issue with current prelink support.
>
> The first patch removes both prelink support by the loader and the
> LD_TRACE_PRELINKING.
>
> The remove of mtrace TRACE_PRELINKING usage is on its own patch
> because it changes LD_TRACE_LOADED_OBJECTS semantic to support
> dumping the executable loading address and fixes mtrace for non
> PIE similar to BZ#22716.
>
> Finally the third part removed LD_USE_LOAD_BIAS, which is used
> solely for try support prelink with PIE.
>
> [1] https://sourceware.org/pipermail/libc-alpha/2022-January/135520.html
> [2] https://sourceware.org/pipermail/libc-alpha/2022-January/135522.html
> [3] https://embed.endfa.net/yocto-cross-prelink-1/
Based on Weekly Call discussion, I will postpone it to 2.36 and sent a
note that 2.35 is latest release that will support prelink.
next prev parent reply other threads:[~2022-01-24 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 17:29 Adhemerval Zanella
2022-01-21 17:29 ` [PATCH 1/3] elf: " Adhemerval Zanella
2022-01-21 17:29 ` [PATCH 2/3] malloc: Remove LD_TRACE_PRELINKING usage from mtrace Adhemerval Zanella
2022-01-21 18:05 ` Siddhesh Poyarekar
2022-01-21 17:29 ` [PATCH 3/3] elf: Remove LD_USE_LOAD_BIAS Adhemerval Zanella
2022-01-24 18:55 ` Adhemerval Zanella [this message]
2022-01-27 4:59 ` [PATCH 0/3] Remove prelink support Carlos O'Donell
2022-02-03 15:29 ` Richard Purdie
2022-02-03 16:30 ` Adhemerval Zanella
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=9ac94bc2-a7aa-decf-290f-c995a156c058@linaro.org \
--to=adhemerval.zanella@linaro.org \
--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).