From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: marcandre.lureau@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] qapi: Fix crash on redefinition with a different condition
Date: Fri, 6 Aug 2021 16:09:02 -0500 [thread overview]
Message-ID: <20210806210902.gorp6sd3suhg4ihe@redhat.com> (raw)
In-Reply-To: <20210806120510.2367124-1-armbru@redhat.com>
On Fri, Aug 06, 2021 at 02:05:10PM +0200, Markus Armbruster wrote:
> QAPISchema._make_implicit_object_type() asserts that when an implicit
> object type is used multiple times, @ifcond is the same for all uses.
> It will be for legitimate uses, i.e. simple union branch wrapper
> types. A comment explains this.
>
> The assertion fails when a command or event is redefined with a
> different condition. The redefinition is an error, but it's flagged
> only later.
>
> Fixing the assertion would complicate matters further. Not
> worthwhile, drop it instead. We really need to get rid of simple
> unions.
>
> Tweak test case redefined-event to cover redefinition with a different
> condition.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
6.2 material (this corner case doesn't fire in our 6.1 code base, and
really only matters for developers adding new interfaces which won't
happen in 6.1).
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2021-08-06 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 12:05 [PATCH] qapi: Fix crash on redefinition with a different condition Markus Armbruster
2021-08-06 21:09 ` 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=20210806210902.gorp6sd3suhg4ihe@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@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 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).