From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jes.Sorensen@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH 2/5] Support human unit formats in strtobytes, eg. 1.0G
Date: Wed, 15 Sep 2010 10:50:50 -0500 [thread overview]
Message-ID: <4C90EB5A.70903@codemonkey.ws> (raw)
In-Reply-To: <4C90EA14.7040801@redhat.com>
On 09/15/2010 10:45 AM, Paolo Bonzini wrote:
> On 09/15/2010 02:23 PM, Jes.Sorensen@redhat.com wrote:
>> switch (*endptr++) {
>> case 'K':
>> case 'k':
>> value<<= 10;
>> break;
>> case 0:
>> + if (divider) {
>> + value = 0;
>> + break;
>> + }
>> case 'M':
>> case 'm':
>> value<<= 20;
>> @@ -284,9 +306,12 @@ uint64_t strtobytes(const char *nptr, char **end)
>> default:
>> value = 0;
>> }
>> + if (divider)
>> + value /= divider;
>>
>
> This risks overflow if you do 1.00000000000000G or something similarly
> braindead. Do we loathe floating point so much that you cannot use
> strtod, like
It should be strtod. Only badness can happen otherwise.
Regards,
Anthony Liguori
> endptr1 = nptr + strspn(s, "0123456789.");
> switch (*endptr1)
> {
> case 0: divider = 1; break;
> case 'm': divider = 1 << 20; break;
> ...
> default: /* error, including for 1.0e+5 and negative */
> }
> value = (uint64_t) (strtod(nptr, &endptr2) / divider);
> if (endptr1 != endptr2) /* error, e.g. 1.2.3 */
>
> return value;
> Paolo
>
next prev parent reply other threads:[~2010-09-15 15:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 12:23 [Qemu-devel] [PATCH 0/5] Introduce strtobytes and make use of it Jes.Sorensen
2010-09-15 12:23 ` [Qemu-devel] [PATCH 1/5] Introduce strtobytes() library function to convert string to byte count Jes.Sorensen
2010-09-15 18:46 ` Andreas Färber
2010-09-15 20:50 ` Stefan Weil
2010-09-15 12:23 ` [Qemu-devel] [PATCH 2/5] Support human unit formats in strtobytes, eg. 1.0G Jes.Sorensen
2010-09-15 14:50 ` [Qemu-devel] " Juan Quintela
2010-09-15 19:29 ` Jes Sorensen
2010-09-15 15:45 ` Paolo Bonzini
2010-09-15 15:50 ` Anthony Liguori [this message]
2010-09-15 19:31 ` Jes Sorensen
2010-09-16 7:19 ` Paolo Bonzini
2010-09-16 10:14 ` Jes Sorensen
2010-09-16 10:40 ` Avi Kivity
2010-09-16 10:42 ` Jes Sorensen
2010-09-16 10:46 ` Avi Kivity
2010-09-16 11:09 ` Paolo Bonzini
2010-09-15 12:23 ` [Qemu-devel] [PATCH 3/5] Add support for 'o' octet (bytes) format as monitor parameter Jes.Sorensen
2010-09-15 12:23 ` [Qemu-devel] [PATCH 4/5] Switch migrate_set_speed() to take an 'o' argument rather than a float Jes.Sorensen
2010-09-15 12:24 ` [Qemu-devel] [PATCH 5/5] Remove obsolete 'f' double parameter type Jes.Sorensen
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=4C90EB5A.70903@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Jes.Sorensen@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).