qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, richard.henderson@linaro.org
Subject: Re: [PATCH v2 15/19] cutils: Set value in all qemu_strtosz* error paths
Date: Fri, 19 May 2023 17:29:55 +0200	[thread overview]
Message-ID: <3fb8db7b-aa51-8701-e0e8-b6b6d37c4c42@redhat.com> (raw)
In-Reply-To: <20230512021033.1378730-16-eblake@redhat.com>

On 12.05.23 04:10, Eric Blake wrote:
> Making callers determine whether or not *value was populated on error
> is not nice for usability.  Pre-patch, we have unit tests that check
> that *result is left unchanged on most EINVAL errors and set to 0 on
> many ERANGE errors.  This is subtly different from libc strtoumax()
> behavior which returns UINT64_MAX on ERANGE errors, as well as
> different from our parse_uint() which slams to 0 on EINVAL on the
> grounds that we want our functions to be harder to mis-use than
> strtoumax().
>
> Let's audit callers:
>
> - hw/core/numa.c:parse_numa() fixed in the previous patch to check for
>    errors
>
> - migration/migration-hmp-cmds.c:hmp_migrate_set_parameter(),
>    monitor/hmp.c:monitor_parse_arguments(),
>    qapi/opts-visitor.c:opts_type_size(),
>    qapi/qobject-input-visitor.c:qobject_input_type_size_keyval(),
>    qemu-img.c:cvtnum_full(), qemu-io-cmds.c:cvtnum(),
>    target/i386/cpu.c:x86_cpu_parse_featurestr(), and
>    util/qemu-option.c:parse_option_size() appear to reject all failures
>    (although some with distinct messages for ERANGE as opposed to
>    EINVAL), so it doesn't matter what is in the value parameter on
>    error.
>
> - All remaining callers are in the testsuite, where we can tweak our
>    expectations to match our new desired behavior.
>
> Advancing to the end of the string parsed on overflow (ERANGE), while
> still returning 0, makes sense (UINT64_MAX as a size is unlikely to be
> useful); likewise, our size parsing code is complex enough that it's
> easier to always return 0 when endptr is NULL but trailing garbage was
> found, rather than trying to return the value of the prefix actually
> parsed (no current caller cared about the value of the prefix).
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
>
> ---
>
> v2: cutils.c unchanged, but rebasing test suite is significant enough
> that I doropped Hanna's R-b
> ---
>   tests/unit/test-cutils.c | 106 +++++++++++++++++++--------------------
>   util/cutils.c            |  17 +++++--
>   2 files changed, 63 insertions(+), 60 deletions(-)

Reviewed-by: Hanna Czenczek <hreitz@redhat.com>



  reply	other threads:[~2023-05-19 15:31 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  2:10 [PATCH v2 00/19] Fix qemu_strtosz() read-out-of-bounds Eric Blake
2023-05-12  2:10 ` [PATCH v2 01/19] test-cutils: Avoid g_assert in unit tests Eric Blake
2023-05-12  3:20   ` Philippe Mathieu-Daudé
2023-05-12 12:11   ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 02/19] test-cutils: Use g_assert_cmpuint where appropriate Eric Blake
2023-05-12  2:10 ` [PATCH v2 03/19] test-cutils: Test integral qemu_strto* value on failures Eric Blake
2023-05-12  2:10 ` [PATCH v2 04/19] test-cutils: Test more integer corner cases Eric Blake
2023-05-19 14:27   ` Hanna Czenczek
2023-05-19 15:17     ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 05/19] cutils: Fix wraparound parsing in qemu_strtoui Eric Blake
2023-05-18 13:34   ` Eric Blake
2023-05-19 14:42   ` Hanna Czenczek
2023-05-19 16:31     ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 06/19] cutils: Document differences between parse_uint and qemu_strtou64 Eric Blake
2023-05-19 14:44   ` Hanna Czenczek
2023-05-12  2:10 ` [PATCH v2 07/19] cutils: Adjust signature of parse_uint[_full] Eric Blake
2023-05-12 16:25   ` Eric Blake
2023-05-19 14:51   ` Hanna Czenczek
2023-05-12  2:10 ` [PATCH v2 08/19] cutils: Allow NULL endptr in parse_uint() Eric Blake
2023-05-12 16:44   ` Eric Blake
2023-05-19 14:54   ` Hanna Czenczek
2023-05-12  2:10 ` [PATCH v2 09/19] test-cutils: Add coverage of qemu_strtod Eric Blake
2023-05-19 15:05   ` Hanna Czenczek
2023-05-19 17:52     ` Eric Blake
2023-05-22 10:56       ` Hanna Czenczek
2023-05-22 12:59         ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 10/19] test-cutils: Prepare for upcoming semantic change in qemu_strtosz Eric Blake
2023-05-12  2:10 ` [PATCH v2 11/19] test-cutils: Refactor qemu_strtosz tests for less boilerplate Eric Blake
2023-05-19 15:13   ` Hanna Czenczek
2023-05-19 17:54     ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 12/19] cutils: Allow NULL str in qemu_strtosz Eric Blake
2023-05-12  3:25   ` Philippe Mathieu-Daudé
2023-05-19 15:15   ` Hanna Czenczek
2023-05-12  2:10 ` [PATCH v2 13/19] numa: Check for qemu_strtosz_MiB error Eric Blake
2023-05-12  2:10 ` [PATCH v2 14/19] test-cutils: Add more coverage to qemu_strtosz11; rgb:1e1e/1e1e/1e1e Eric Blake
2023-05-19 15:26   ` [PATCH v2 14/19] test-cutils: Add more coverage to qemu_strtosz11;rgb:1e1e/1e1e/1e1e Hanna Czenczek
2023-05-19 18:02     ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 15/19] cutils: Set value in all qemu_strtosz* error paths Eric Blake
2023-05-19 15:29   ` Hanna Czenczek [this message]
2023-05-12  2:10 ` [PATCH v2 16/19] cutils: Set value in all integral qemu_strto* " Eric Blake
2023-05-12  2:10 ` [PATCH v2 17/19] cutils: Use parse_uint in qemu_strtosz for negative rejection Eric Blake
2023-05-12 19:34   ` Eric Blake
2023-05-19 15:32     ` Hanna Czenczek
2023-05-12  2:10 ` [PATCH v2 18/19] cutils: Improve qemu_strtod* error paths Eric Blake
2023-05-18 13:47   ` Eric Blake
2023-05-12  2:10 ` [PATCH v2 19/19] cutils: Improve qemu_strtosz handling of fractions Eric Blake
2023-05-19 15:36   ` Hanna Czenczek
2023-05-12 12:24 ` [PATCH v2 00/19] Fix qemu_strtosz() read-out-of-bounds Eric Blake

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=3fb8db7b-aa51-8701-e0e8-b6b6d37c4c42@redhat.com \
    --to=hreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).