From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Binutils Mailing List <binutils@sourceware.org>,
gdb@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: Threat model for GNU Binutils
Date: Fri, 14 Apr 2023 16:07:44 +0100 [thread overview]
Message-ID: <ff05645f-4089-5630-ff20-803002bcf48d@foss.arm.com> (raw)
In-Reply-To: <78f3e6a6-dec2-3aa2-d1b6-935d842add1e@gotplt.org>
On 14/04/2023 15:08, Siddhesh Poyarekar wrote:
> There's also a (rare) possibility of an infrequently used instruction
> having incorrect opcode mapping, resulting in a bug being masked when
> dumped with objdump or resulting code having undefined behaviour.
The best way to deal with this risk is to run test binaries generated by
the tools through an independently developed toolchain; something I
mentioned in the mitigation section. The chances of a common-mode
failure leading to the same bug in both sets of tools is very low.
R.
prev parent reply other threads:[~2023-04-14 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 13:12 Richard Earnshaw
2023-04-14 14:08 ` Siddhesh Poyarekar
2023-04-14 14:41 ` Richard Earnshaw
2023-04-17 16:17 ` Siddhesh Poyarekar
2023-04-17 16:22 ` Siddhesh Poyarekar
2023-04-14 15:07 ` Richard Earnshaw [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=ff05645f-4089-5630-ff20-803002bcf48d@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nickc@redhat.com \
--cc=siddhesh@gotplt.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).