From: Luiz Capitulino <lcapitulino@redhat.com>
To: aliguori@us.ibm.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 5/6] hmp: expr_unary(): check for overflow in strtoul()/strtoull()
Date: Tue, 8 May 2012 14:50:17 -0300 [thread overview]
Message-ID: <1336499418-12722-6-git-send-email-lcapitulino@redhat.com> (raw)
In-Reply-To: <1336499418-12722-1-git-send-email-lcapitulino@redhat.com>
It's not checked currently, so something like:
(qemu) balloon -100000000000001111114334234
(qemu)
Will just "work" (in this case the balloon command will get a random
value).
Fix it by checking if strtoul()/strtoull() overflowed.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
---
monitor.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/monitor.c b/monitor.c
index 8946a10..bf60984 100644
--- a/monitor.c
+++ b/monitor.c
@@ -3120,11 +3120,15 @@ static int64_t expr_unary(Monitor *mon)
n = 0;
break;
default:
+ errno = 0;
#if TARGET_PHYS_ADDR_BITS > 32
n = strtoull(pch, &p, 0);
#else
n = strtoul(pch, &p, 0);
#endif
+ if (errno == ERANGE) {
+ expr_error(mon, "number too large");
+ }
if (pch == p) {
expr_error(mon, "invalid char in expression");
}
--
1.7.9.2.384.g4a92a
next prev parent reply other threads:[~2012-05-08 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 17:50 [Qemu-devel] [PULL 1.1 0/6]: QMP queue Luiz Capitulino
2012-05-08 17:50 ` [Qemu-devel] [PULL 1/6] wakeup on migration Luiz Capitulino
2012-05-08 17:50 ` [Qemu-devel] [PULL 2/6] qapi-schema.json: fix RunState enums alphabetical order Luiz Capitulino
2012-05-08 17:50 ` [Qemu-devel] [PULL 3/6] runstate: introduce suspended state Luiz Capitulino
2012-05-08 17:50 ` [Qemu-devel] [PULL 4/6] vl: drop is_suspended variable Luiz Capitulino
2012-05-08 17:50 ` Luiz Capitulino [this message]
2012-05-08 17:50 ` [Qemu-devel] [PULL 6/6] hmp: fix bad value conversion for M type Luiz Capitulino
2012-05-09 18:59 ` [Qemu-devel] [PULL 1.1 0/6]: QMP queue Anthony Liguori
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=1336499418-12722-6-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--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).