From: Markus Armbruster <armbru@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Igor Mammedov <imammedo@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v3 1/7] qapi: use qemu_strtoi64() in parse_str
Date: Wed, 31 Oct 2018 15:40:12 +0100 [thread overview]
Message-ID: <87pnvqdvsj.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20181023152306.3123-2-david@redhat.com> (David Hildenbrand's message of "Tue, 23 Oct 2018 17:23:00 +0200")
David Hildenbrand <david@redhat.com> writes:
> The qemu api claims to be easier to use, and the resulting code seems to
> agree.
Ah, an opportunity to nitpick spelling! "The QEMU API", and "qapi: Use
qemu_strtoi64() ..."
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> qapi/string-input-visitor.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/qapi/string-input-visitor.c b/qapi/string-input-visitor.c
> index b3fdd0827d..c1454f999f 100644
> --- a/qapi/string-input-visitor.c
> +++ b/qapi/string-input-visitor.c
> @@ -20,6 +20,7 @@
> #include "qemu/option.h"
> #include "qemu/queue.h"
> #include "qemu/range.h"
> +#include "qemu/cutils.h"
>
>
> struct StringInputVisitor
> @@ -46,10 +47,10 @@ static void free_range(void *range, void *dummy)
>
> static int parse_str(StringInputVisitor *siv, const char *name, Error **errp)
> {
> - char *str = (char *) siv->string;
> - long long start, end;
> + const char *str = (char *) siv->string;
And an opportunity to nitpick whitespace! Drop the space between (char
*) and siv->string while there.
> + const char *endptr;
> + int64_t start, end;
> Range *cur;
> - char *endptr;
>
> if (siv->ranges) {
> return 0;
> @@ -60,9 +61,7 @@ static int parse_str(StringInputVisitor *siv, const char *name, Error **errp)
> }
>
> do {
> - errno = 0;
> - start = strtoll(str, &endptr, 0);
> - if (errno == 0 && endptr > str) {
> + if (!qemu_strtoi64(str, &endptr, 0, &start)) {
> if (*endptr == '\0') {
> cur = g_malloc0(sizeof(*cur));
> range_set_bounds(cur, start, start);
> @@ -71,11 +70,7 @@ static int parse_str(StringInputVisitor *siv, const char *name, Error **errp)
> str = NULL;
> } else if (*endptr == '-') {
> str = endptr + 1;
> - errno = 0;
> - end = strtoll(str, &endptr, 0);
> - if (errno == 0 && endptr > str && start <= end &&
> - (start > INT64_MAX - 65536 ||
> - end < start + 65536)) {
> + if (!qemu_strtoi64(str, &endptr, 0, &end) && start < end) {
You deleted (start > INT64_MAX - 65536 || end < start + 65536). Can you
explain that to me? I'm feeling particularly dense today...
> if (*endptr == '\0') {
> cur = g_malloc0(sizeof(*cur));
> range_set_bounds(cur, start, end);
next prev parent reply other threads:[~2018-10-31 14:40 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 15:22 [Qemu-devel] [PATCH v3 0/7] qapi/range/memory-device: fixes and cleanups David Hildenbrand
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 1/7] qapi: use qemu_strtoi64() in parse_str David Hildenbrand
2018-10-25 14:37 ` David Gibson
2018-10-31 14:40 ` Markus Armbruster [this message]
2018-10-31 16:47 ` David Hildenbrand
2018-10-31 17:55 ` Markus Armbruster
2018-10-31 18:01 ` David Hildenbrand
2018-11-05 15:37 ` Markus Armbruster
2018-11-05 15:53 ` David Hildenbrand
2018-11-05 16:48 ` Eric Blake
2018-11-06 9:20 ` David Hildenbrand
2018-11-05 20:43 ` Markus Armbruster
2018-11-06 9:19 ` David Hildenbrand
2018-11-07 15:29 ` Markus Armbruster
2018-11-07 20:02 ` David Hildenbrand
2018-11-08 8:39 ` Markus Armbruster
2018-11-08 8:54 ` David Hildenbrand
2018-11-08 9:13 ` Markus Armbruster
2018-11-08 13:05 ` David Hildenbrand
2018-11-08 14:36 ` Markus Armbruster
2018-11-08 14:46 ` David Hildenbrand
2018-11-08 14:42 ` Eric Blake
2018-11-08 14:49 ` David Hildenbrand
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 2/7] qapi: correctly parse uint64_t values from strings David Hildenbrand
2018-10-25 14:41 ` David Gibson
2018-10-26 12:48 ` David Hildenbrand
2018-10-31 14:32 ` Markus Armbruster
2018-10-31 14:44 ` Markus Armbruster
2018-10-31 17:19 ` David Hildenbrand
2018-10-31 17:18 ` David Hildenbrand
2018-11-04 3:27 ` David Gibson
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 3/7] range: pass const pointer where possible David Hildenbrand
2018-10-25 14:41 ` David Gibson
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 4/7] range: add some more functions David Hildenbrand
2018-11-01 10:00 ` Igor Mammedov
2018-11-01 10:29 ` David Hildenbrand
2018-11-01 11:05 ` Igor Mammedov
2018-11-05 10:30 ` David Hildenbrand
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 5/7] memory-device: use QEMU_IS_ALIGNED David Hildenbrand
2018-10-25 14:44 ` David Gibson
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 6/7] memory-device: avoid overflows on very huge devices David Hildenbrand
2018-10-25 14:44 ` David Gibson
2018-10-25 14:45 ` Igor Mammedov
2018-10-23 15:23 ` [Qemu-devel] [PATCH v3 7/7] memory-device: rewrite address assignment using ranges David Hildenbrand
2018-11-12 14:07 ` David Hildenbrand
2018-11-13 12:26 ` Igor Mammedov
2018-11-13 12:41 ` David Hildenbrand
2018-11-13 13:01 ` [Qemu-devel] [PATCH v4] " David Hildenbrand
2018-10-31 10:14 ` [Qemu-devel] [PATCH v3 0/7] qapi/range/memory-device: fixes and cleanups David Hildenbrand
2018-10-31 19:43 ` Eduardo Habkost
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=87pnvqdvsj.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.