From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] binutils: add patch for 2.27 that fixes elf2flt segfaults
Date: Thu, 13 Apr 2017 19:18:57 +0200 [thread overview]
Message-ID: <20170413171857.GA11446@waldemar-brodkorb.de> (raw)
In-Reply-To: <579cec15-214a-978c-85ca-1f471f104deb@mind.be>
Hi,
Arnout Vandecappelle wrote,
>
>
> On 13-04-17 09:36, Thomas Petazzoni wrote:
> > Hello,
> >
> > On Mon, 10 Apr 2017 10:42:38 +0200, Arnout Vandecappelle
> > (Essensium/Mind) wrote:
> >
> >> .../2.27/0011-arm-thumb-fix-elf2flt-segfault.patch | 927 +++++++++++++++++++++
> >> 1 file changed, 927 insertions(+)
> >> create mode 100644 package/binutils/2.27/0011-arm-thumb-fix-elf2flt-segfault.patch
> >
> > Thanks a lot for doing the bisection! However, this is really a big
> > patch.
>
> Yes...
>
> > Do we understand what it does?
>
> I've tried, but... no. The great thing about this patch is that its purpose is
> to add support for entering/exiting Secure Mode on ARMv8. So this really
> shouldn't impact a Cortex-M4...
>
> > Do we know if it is safe to
> > backport it on 2.27 without other patches?
>
> Nope :-)
>
> > Isn't there a more minimal fix for binutils 2.27?
>
> Possibly. Is someone here somewhat familiar with elf2flt? Waldemar?
No Sorry. Either you might ask on the mailinglist (uclinux) or we
could just skip 2.27 and move on..
best regards
Waldemar
next prev parent reply other threads:[~2017-04-13 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 8:42 [Buildroot] [PATCH 1/2] binutils: rewrite 2.27 patches as proper git formatted Arnout Vandecappelle
2017-04-10 8:42 ` [Buildroot] [PATCH 2/2] binutils: add patch for 2.27 that fixes elf2flt segfaults Arnout Vandecappelle
2017-04-13 7:36 ` Thomas Petazzoni
2017-04-13 13:29 ` Arnout Vandecappelle
2017-04-13 17:18 ` Waldemar Brodkorb [this message]
2017-04-13 21:11 ` Arnout Vandecappelle
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=20170413171857.GA11446@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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