qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] test-qobject-input-visitor: Cover visit_type_uint64()
Date: Tue, 21 Mar 2017 13:11:00 -0500	[thread overview]
Message-ID: <37080340-bd84-ec1b-6a43-584eb1e31f76@redhat.com> (raw)
In-Reply-To: <1490118290-6133-1-git-send-email-armbru@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]

On 03/21/2017 12:44 PM, Markus Armbruster wrote:
> The new test demonstrates known bugs: integers between INT64_MAX+1 and
> UINT64_MAX rejected, and integers between INT64_MIN and -1 are
> accepted modulo 2^64.
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
>  tests/test-qobject-input-visitor.c | 30 ++++++++++++++++++++++++++++++
>  1 file changed, 30 insertions(+)
> 
> diff --git a/tests/test-qobject-input-visitor.c b/tests/test-qobject-input-visitor.c
> index 6eb48fe..f965743 100644
> --- a/tests/test-qobject-input-visitor.c
> +++ b/tests/test-qobject-input-visitor.c
> @@ -116,6 +116,34 @@ static void test_visitor_in_int(TestInputVisitorData *data,
>      g_assert_cmpint(res, ==, value);
>  }
>  
> +static void test_visitor_in_uint(TestInputVisitorData *data,
> +                                const void *unused)
> +{
> +    Error *err = NULL;
> +    uint64_t res = 0;
> +    int value = 42;
> +    Visitor *v;
> +
> +    v = visitor_input_test_init(data, "%d", value);

Another place where I have to rebase my work that gets rid of the
dynamic JSON parser, if we want to revive that patch series; but don't
let it stop you on this patch.

> +
> +    visit_type_uint64(v, NULL, &res, &error_abort);
> +    g_assert_cmpuint(res, ==, (uint64_t)value);
> +
> +    /* BUG: value between INT64_MIN and -1 accepted modulo 2^64 */
> +
> +    v = visitor_input_test_init(data, "%d", -value);

Not necessarily a bug - libvirt exploits this behavior.  So even if we
fix the real bug, namely...

> +
> +    visit_type_uint64(v, NULL, &res, &error_abort);
> +    g_assert_cmpuint(res, ==, (uint64_t)-value);
> +
> +    /* BUG: value between INT64_MAX+1 and UINT64_MAX rejected */
> +
> +    v = visitor_input_test_init(data, "18446744073709551574");

...this, we may be stuck keeping the modulo 2^64 parsing around for
back-compat.

At any rate, your test is a welcome addition; and as it only touches the
testsuite, it is still 2.9 material if desired.
Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

      reply	other threads:[~2017-03-21 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 17:44 [Qemu-devel] [PATCH] test-qobject-input-visitor: Cover visit_type_uint64() Markus Armbruster
2017-03-21 18:11 ` Eric Blake [this message]

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=37080340-bd84-ec1b-6a43-584eb1e31f76@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mdroth@linux.vnet.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).