From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: ben@skyportsystems.com, qemu-devel@nongnu.org,
peter.maydell@linaro.org, armbru@redhat.com, dgilbert@redhat.com,
pbonzini@redhat.com, imammedo@redhat.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Bugfix: Handle error if VM Generation ID device not present
Date: Thu, 2 Mar 2017 23:45:49 +0200 [thread overview]
Message-ID: <20170302234513-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <24c55319-20af-fbe2-366b-e3bda17f6f94@redhat.com>
On Thu, Mar 02, 2017 at 03:41:33PM -0600, Eric Blake wrote:
> On 03/02/2017 03:36 PM, ben@skyportsystems.com wrote:
> > From: Ben Warren <ben@skyportsystems.com>
> >
> > This was crashing due to NULL-pointer dereference
> >
> > QMP Test case:
> > ==============
> >
> > (QEMU) query-vm-generation-id
> > {"error": {"class": "GenericError", "desc": "VM Generation ID device not
> > found"}}
> >
> > HMP Test case:
> > ==============
> > virsh # qemu-monitor-command --hmp 3 info vm-generation-id
> > VM Generation ID device not found
> >
> > Signed-off-by: Ben Warren <ben@skyportsystems.com>
> > ---
> > hmp.c | 4 +++-
> > hw/acpi/vmgenid.c | 1 +
> > 2 files changed, 4 insertions(+), 1 deletion(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> However, hw/acpi/vmgenid.c is not part of the tree yet, so it may be
> better to just respin the pull request to incorporate this into the
> problematic patch that introduced the problem, rather than needing a
> followup patch.
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
The issue seems minor enough.
I don't plan to re-spin unless there are more issues.
--
MST
next prev parent reply other threads:[~2017-03-02 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 21:36 [Qemu-devel] [PATCH] Bugfix: Handle error if VM Generation ID device not present ben
2017-03-02 21:41 ` Eric Blake
2017-03-02 21:45 ` Michael S. Tsirkin [this message]
2017-03-02 22:41 ` Laszlo Ersek
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=20170302234513-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=ben@skyportsystems.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).