From: Eduardo Habkost <ehabkost@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
david@redhat.com, "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.11 v3 0/2] Check for the availability of a hotplug controller before adding a device
Date: Tue, 9 Jan 2018 18:09:26 -0200 [thread overview]
Message-ID: <20180109200926.GC18022@localhost.localdomain> (raw)
In-Reply-To: <c70ea44b-8eb8-2336-7263-77967056265d@redhat.com>
On Mon, Dec 18, 2017 at 12:59:50PM +0100, Thomas Huth wrote:
> On 02.11.2017 11:10, Thomas Huth wrote:
> > First patch is a small clean up to the error handling code in
> > qdev_device_add(), and the second patch adds a proper check for
> > the availability of a hotplug controller to prevent the possibility
> > of a crash with device_del.
> >
> > The crash can currently be triggered for example like this:
> >
> > $ s390x-softmmu/qemu-system-s390x -M none -nographic
> > QEMU 2.10.50 monitor - type 'help' for more information
> > (qemu) device_add qemu-s390x-cpu,id=x
> > (qemu) device_del x
> > **
> > ERROR:qemu/qdev-monitor.c:872:qdev_unplug: assertion failed: (hotplug_ctrl)
> > Aborted (core dumped)
> >
> > v3:
> > - Invert the logic of the second error check in the first patch
> > as suggested by Igor
> > - Updated the patch description of the second patch with the current
> > way to crash QEMU
> >
> > v2:
> > - Do the check for the availability of the hotplug controller earlier
> > in qdev_device_add
> > - Use common new err_dev_del handler in case of failure
> >
> > Thomas Huth (2):
> > qdev_monitor: Simplify error handling in qdev_device_add()
> > qdev: Check for the availability of a hotplug controller before adding
> > a device
> >
> > hw/core/qdev.c | 28 ++++++++++++++++++++--------
> > include/hw/qdev-core.h | 1 +
> > qdev-monitor.c | 21 +++++++++++++--------
> > 3 files changed, 34 insertions(+), 16 deletions(-)
>
> Ping!
>
> Paolo or Eduardo, could one of you please pick up the two patches?
Very sorry for the long delay. I just queued it on machine-next.
Thanks!
--
Eduardo
prev parent reply other threads:[~2018-01-09 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 10:10 [Qemu-devel] [PATCH for-2.11 v3 0/2] Check for the availability of a hotplug controller before adding a device Thomas Huth
2017-11-02 10:10 ` [Qemu-devel] [PATCH v3 1/2] qdev_monitor: Simplify error handling in qdev_device_add() Thomas Huth
2017-11-07 14:01 ` Cornelia Huck
2017-11-02 10:10 ` [Qemu-devel] [PATCH v3 2/2] qdev: Check for the availability of a hotplug controller before adding a device Thomas Huth
2017-11-07 14:17 ` Cornelia Huck
2017-11-13 14:00 ` Markus Armbruster
2017-11-13 14:12 ` Thomas Huth
2017-12-18 11:59 ` [Qemu-devel] [PATCH for-2.11 v3 0/2] " Thomas Huth
2018-01-09 20:09 ` Eduardo Habkost [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=20180109200926.GC18022@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).