Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: powerpc32 transition to secureplt
Date: Tue, 29 Sep 2020 21:09:23 +0200	[thread overview]
Message-ID: <87d024v1r0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANQCQpY+au2CO5iLonnz7cUc8L-1C=XhL2pWAZ=bJBQUZ=K23g@mail.gmail.com> (Matthew Weber's message of "Wed, 23 Sep 2020 14:01:44 -0500")

>>>>> "Matthew" == Matthew Weber <matthew.weber@rockwellcollins.com> writes:

 > Peter,
 > On Wed, Sep 23, 2020 at 10:29 AM Matt Weber
 > <matthew.weber@rockwellcollins.com> wrote:
 >> 
 >> PowerPC has two PLT models: BSS-PLT and Secure-PLT. BSS-PLT uses
 >> runtime code generation to generate the PLT stubs. Secure-PLT was
 >> introduced with GCC 4.1 and Binutils 2.17 (base has GCC 4.2.1 and
 >> Binutils 2.17), and is a more secure PLT format, using a read-only
 >> linkage table, with the dynamic linker populating a non-executable
 >> index table.
 >> 
 >> Ref to other distro/BSD transitions
 >> https://patchwork.openembedded.org/patch/106621/
 >> https://reviews.freebsd.org/D20598
 >> 
 >> Fixes a bug observed when creating SELinux policy where all apps
 >> require execmem because the heap requires execute before this
 >> change.
 >> 

 > This also applies to 2020.02.x and the previous release 2020.08.

Committed to 2020.02.x, 2020.05.x and 2020.08.x, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2020-09-29 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 15:29 [Buildroot] [PATCH] gcc: powerpc32 transition to secureplt Matt Weber
2020-09-23 18:51 ` Thomas Petazzoni
2020-09-23 19:01 ` Matthew Weber
2020-09-29 19:09   ` Peter Korsgaard [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=87d024v1r0.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox