From: Luiz Capitulino <lcapitulino@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: famz@redhat.com, qemu-stable@nongnu.org, armbru@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] qapi: fix crash in dealloc visitor for union types
Date: Fri, 19 Sep 2014 13:52:17 -0400 [thread overview]
Message-ID: <20140919135217.4b473d78@redhat.com> (raw)
In-Reply-To: <1411072603-8984-1-git-send-email-mdroth@linux.vnet.ibm.com>
On Thu, 18 Sep 2014 15:36:39 -0500
Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> This series introduces visit_start_union and visit_end_union as a way
> of allowing visitors to trigger generated code to bail out on visiting
> union fields if the visitor implementation deems doing so to be unsafe.
>
> See patch 1 for the circumstances that cause the segfault in the
> dealloc visitor.
>
> This is a spin-off of a patch submitted by Fam Zheng earlier. See the
> thread for additional background on why we're taking this approach:
>
> http://thread.gmane.org/gmane.comp.emulators.qemu/296090
Applied to the qmp branch, thanks.
PS: Michael, I'm assuming you were not planning to send a pull yourself.
If that's not the case, please let me know.
>
> v3:
> * fixed up commit msg in patch #2 (Eric)
> * rebased on latest master
>
> v2:
> * added comments to clarify true/false visit_start_union vs. errp
> in dealloc visitor implementation (Eric)
> * fixed a line that was >80 characters (Eric)
> * fixed extra period in patch 2 commit msg (Eric)
> * added comments to note reasons why the interface is useable for
> dealloc visitor, but may require extra QAPI groundwork and
> interface parameters to be useful for other types of visitors
> * included Fam's qemu-iotest test case to exercise bug fix in a
> user-triggerable scenario.
>
> include/qapi/visitor-impl.h | 2 ++
> include/qapi/visitor.h | 2 ++
> qapi/qapi-dealloc-visitor.c | 26 +++++++++++++++++++++++
> qapi/qapi-visit-core.c | 15 +++++++++++++
> scripts/qapi-visit.py | 6 ++++++
> tests/qapi-schema/qapi-schema-test.json | 10 +++++++++
> tests/qapi-schema/qapi-schema-test.out | 3 +++
> tests/qemu-iotests/087 | 17 +++++++++++++++
> tests/qemu-iotests/087.out | 13 ++++++++++++
> tests/test-qmp-input-strict.c | 17 +++++++++++++++
> 10 files changed, 111 insertions(+)
>
next prev parent reply other threads:[~2014-09-19 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 20:36 [Qemu-devel] [PATCH v3 0/4] qapi: fix crash in dealloc visitor for union types Michael Roth
2014-09-18 20:36 ` [Qemu-devel] [PATCH v3 1/4] qapi: add visit_start_union and visit_end_union Michael Roth
2014-09-18 20:36 ` [Qemu-devel] [PATCH v3 2/4] qapi: dealloc visitor, implement visit_start_union Michael Roth
2014-09-18 20:36 ` [Qemu-devel] [PATCH v3 3/4] tests: add QMP input visitor test for unions with no discriminator Michael Roth
2014-09-18 20:36 ` [Qemu-devel] [PATCH v3 4/4] qemu-iotests: Test missing "driver" key for blockdev-add Michael Roth
2014-09-19 17:52 ` Luiz Capitulino [this message]
2014-09-19 18:21 ` [Qemu-devel] [PATCH v3 0/4] qapi: fix crash in dealloc visitor for union types Michael Roth
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=20140919135217.4b473d78@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).