From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Richard Henderson <rth@twiddle.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PATCH for-2.9 6/6] disas/arm: Avoid unintended sign extension
Date: Fri, 3 Mar 2017 15:50:33 +0000 [thread overview]
Message-ID: <1488556233-31246-7-git-send-email-peter.maydell@linaro.org> (raw)
In-Reply-To: <1488556233-31246-1-git-send-email-peter.maydell@linaro.org>
When assembling 'given' from the instruction bytes, C's integer
promotion rules mean we may promote an unsigned char to a signed
integer before shifting it, and then sign extend to a 64-bit long,
which can set the high bits of the long. The code doesn't in fact
care about the high bits if the long is 64 bits, but this is
surprising, so don't do it.
(Spotted by Coverity, CID 1005404.)
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
Arguably 'given' should be uint32_t here rather than 'long', but a
small change to placate Coverity seemed wiser than a wholesale change
of the type of the 'given' variables/arguments through the whole
file, since this is 3rd-party code that's known to work.
---
disas/arm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/disas/arm.c b/disas/arm.c
index 93c6503..27396dd 100644
--- a/disas/arm.c
+++ b/disas/arm.c
@@ -3901,9 +3901,9 @@ print_insn_arm (bfd_vma pc, struct disassemble_info *info)
status = info->read_memory_func (pc, (bfd_byte *)b, 4, info);
if (little)
- given = (b[0]) | (b[1] << 8) | (b[2] << 16) | (b[3] << 24);
+ given = (b[0]) | (b[1] << 8) | (b[2] << 16) | ((unsigned)b[3] << 24);
else
- given = (b[3]) | (b[2] << 8) | (b[1] << 16) | (b[0] << 24);
+ given = (b[3]) | (b[2] << 8) | (b[1] << 16) | ((unsigned)b[0] << 24);
}
else
{
--
2.7.4
next prev parent reply other threads:[~2017-03-03 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 15:50 [Qemu-devel] [PATCH for-2.9 0/6] disas: Fix various coverity nits Peter Maydell
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 1/6] disas/hppa: Remove dead code Peter Maydell
2017-03-03 19:40 ` Philippe Mathieu-Daudé
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 2/6] disas/i386: Avoid NULL pointer dereference in error case Peter Maydell
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 3/6] disas/m68k: Avoid unintended sign extension in get_field() Peter Maydell
2017-03-03 18:56 ` Laurent Vivier
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 4/6] disas/microblaze: Avoid unintended sign extension Peter Maydell
2017-03-03 15:58 ` Edgar E. Iglesias
2017-03-03 16:02 ` Peter Maydell
2017-03-03 16:06 ` Edgar E. Iglesias
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 5/6] disas/cris: " Peter Maydell
2017-03-03 15:58 ` Edgar E. Iglesias
2017-03-03 19:43 ` Philippe Mathieu-Daudé
2017-03-03 15:50 ` Peter Maydell [this message]
2017-03-03 16:11 ` [Qemu-devel] [PATCH for-2.9 0/6] disas: Fix various coverity nits no-reply
2017-03-04 0:00 ` no-reply
2017-03-04 12:44 ` Peter Maydell
2017-03-06 1:03 ` Fam Zheng
2017-03-07 17:06 ` Peter Maydell
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=1488556233-31246-7-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=edgar.iglesias@gmail.com \
--cc=ehabkost@redhat.com \
--cc=laurent@vivier.eu \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.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;
as well as URLs for NNTP newsgroup(s).