From: Onur Sahin <onursahin08@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, Onur Sahin <onursahin08@gmail.com>
Subject: [Qemu-devel] [PATCH] target-arm: Check undefined opcodes for SWP in A32 decoder
Date: Thu, 22 Mar 2018 23:58:29 -0400 [thread overview]
Message-ID: <1521777509-22896-1-git-send-email-onursahin08@gmail.com> (raw)
Hi all,
I have noticed that the decoding part in ARM/A32 does not verify the
opcodes for SWP instructions. The opcode field ([23:20]) for SWP
instructions should be 0 or 4, and QEMU does not check against these
values.
Other opcode values less than 8 are Undefined within the encoding
space of sychronization primitives (e.g., SWP, LDREX*). See section
A5.2.10 of ARMv7-A manual for reference. Because of the missing opcode
check, QEMU happily executes these Undefined cases as a SWP instruction.
The following fix adds proper opcode checks before assuming a valid SWP.
Best,
Onur
Signed-off-by: Onur Sahin <onursahin08@gmail.com>
---
target-arm/translate.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target-arm/translate.c b/target-arm/translate.c
index bd5d5cb..fb31c12 100644
--- a/target-arm/translate.c
+++ b/target-arm/translate.c
@@ -8831,7 +8831,7 @@ static void disas_arm_insn(DisasContext *s, unsigned int insn)
}
}
tcg_temp_free_i32(addr);
- } else {
+ } else if (!(insn & 0x00B00000)) {
/* SWP instruction */
rm = (insn) & 0xf;
@@ -8852,6 +8852,9 @@ static void disas_arm_insn(DisasContext *s, unsigned int insn)
tcg_temp_free_i32(addr);
store_reg(s, rd, tmp2);
}
+ else {
+ goto illegal_op;
+ }
}
} else {
int address_offset;
--
1.8.3.1
next reply other threads:[~2018-03-23 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 3:58 Onur Sahin [this message]
2018-03-23 11:50 ` [Qemu-devel] [Qemu-arm] [PATCH] target-arm: Check undefined opcodes for SWP in A32 decoder Peter Maydell
2018-03-23 21:43 ` [Qemu-devel] [PATCH v2] " Onur Sahin
2018-04-05 12:26 ` 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=1521777509-22896-1-git-send-email-onursahin08@gmail.com \
--to=onursahin08@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).