From: Jan Beulich <jbeulich@suse.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: "richard.earnshaw@arm.com" <richard.earnshaw@arm.com>,
"ramana.radhakrishnan@arm.com" <ramana.radhakrishnan@arm.com>,
Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] arm: fix array-out-of-bounds upon register parsing error
Date: Thu, 10 Jun 2021 12:45:16 +0200 [thread overview]
Message-ID: <860baeab-c4c0-1ef1-8b4d-db69a3314dd3@suse.com> (raw)
In-Reply-To: <cf8b59f7-a933-75fa-d2d3-34e784a3f88a@foss.arm.com>
On 10.06.2021 12:29, Richard Earnshaw wrote:
> OK.
Thanks, committed.
> I wonder if we could somehow build in an assert to check this. Even
> better would be a static assertion during compilation, but that might be
> harder.
A Linux-like (or wherever its origin) BUILD_BUG_ON() shouldn't be that
hard to put in, even if _Static_assert() can't be used (unconditionally)
just yet.
Jan
prev parent reply other threads:[~2021-06-10 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 7:43 Jan Beulich
2021-06-10 10:29 ` Richard Earnshaw
2021-06-10 10:45 ` Jan Beulich [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=860baeab-c4c0-1ef1-8b4d-db69a3314dd3@suse.com \
--to=jbeulich@suse.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@arm.com \
/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).