From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: bkylerussell@gmail.com, Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] security_flags.inc: don't default to PIE if image-prelink is enabled
Date: Thu, 20 Jan 2022 20:43:07 +0000 [thread overview]
Message-ID: <2fd0eb95185feb18e75c4570a4f71bb6188ee3f1.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAFrQVPMvR0QnLan+=bdi0ZmgTpCxmz=-SZQxyTuEcm6=OTDmmw@mail.gmail.com>
On Thu, 2022-01-20 at 12:41 -0500, bkylerussell@gmail.com wrote:
> Yes, we do use prelink. I think our use case primarily benefits from CoW
> memory savings, rather than load times. Of course, GCCPIE can be overridden
> in the distro layer, but seeing as image-prelink.bbclass still exists
> upstream, the default definition should support configurations that choose to
> enable it.
It would seem that glibc plan to remove prelink support in 2.36. If anyone wants
it to stick around they need to convince the glibc developers not to do that as
I don't think we'd be able to sustain it if it is removed there.
I'm seriously considering removing prelink from OE-Core before the LTS at this
point given the position glibc has and the lack of maintenance prelink clearly
has in OE :(.
Cheers,
Richard
next prev parent reply other threads:[~2022-01-20 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 3:30 [PATCH] security_flags.inc: don't default to PIE if image-prelink is enabled Kyle Russell
2022-01-20 8:30 ` [OE-core] " Alexander Kanavin
2022-01-20 17:41 ` Kyle Russell
2022-01-20 20:43 ` Richard Purdie [this message]
2022-01-20 20:51 ` Peter Kjellerstedt
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=2fd0eb95185feb18e75c4570a4f71bb6188ee3f1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=bkylerussell@gmail.com \
--cc=openembedded-core@lists.openembedded.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 NNTP newsgroup(s).