From: Chris Friedt <chrisfriedt@gmail.com>
To: qemu-devel@nongnu.org
Cc: cfriedt@meta.com, jslaby@suse.cz, Chris Friedt <chrisfriedt@gmail.com>
Subject: [PATCH] hw: misc: edu: fix 2 off-by-one errors
Date: Fri, 14 Oct 2022 12:12:47 -0400 [thread overview]
Message-ID: <20221014161247.38843-1-chrisfriedt@gmail.com> (raw)
In the case that size1 was zero, because of the explicit
'end1 > addr' check, the range check would fail and the error
message would read as shown below. The correct comparison
is 'end1 >= addr' (or 'addr <= end1').
EDU: DMA range 0x40000-0x3ffff out of bounds (0x40000-0x3ffff)!
At the opposite end, in the case that size1 was 4096, within()
would fail because of the non-inclusive check 'end1 < end2',
which should have been 'end1 <= end2'. The error message would
previously say
EDU: DMA range 0x40000-0x40fff out of bounds (0x40000-0x40fff)!
Note: the original change (and error message) was when parameters
were uint32_t.
Signed-off-by: Chris Friedt <chrisfriedt@gmail.com>
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1254
---
hw/misc/edu.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/hw/misc/edu.c b/hw/misc/edu.c
index e935c418d4..a6f5f97f13 100644
--- a/hw/misc/edu.c
+++ b/hw/misc/edu.c
@@ -103,19 +103,18 @@ static void edu_lower_irq(EduState *edu, uint32_t val)
}
}
-static bool within(uint64_t addr, uint64_t start, uint64_t end)
-{
- return start <= addr && addr < end;
-}
-
static void edu_check_range(uint64_t addr, uint64_t size1, uint64_t start,
uint64_t size2)
{
uint64_t end1 = addr + size1;
uint64_t end2 = start + size2;
- if (within(addr, start, end2) &&
- end1 > addr && within(end1, start, end2)) {
+ /*
+ * 1. ensure we aren't overflowing
+ * 2. ensure that [start, end2) is within [addr, end1)
+ */
+ if (end1 >= addr && end2 >= start && start >= addr && end2 <= end1)
+ {
return;
}
--
2.36.1
next reply other threads:[~2022-10-14 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 16:12 Chris Friedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-09 2:37 [PATCH] hw: misc: edu: fix 2 off-by-one errors Christopher Friedt
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=20221014161247.38843-1-chrisfriedt@gmail.com \
--to=chrisfriedt@gmail.com \
--cc=cfriedt@meta.com \
--cc=jslaby@suse.cz \
--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).