From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix MSI memory region use after tree
Date: Sun, 6 Jul 2014 09:12:04 +0300 [thread overview]
Message-ID: <20140706061204.GA6461@redhat.com> (raw)
In-Reply-To: <20140706053953.GA5007@redhat.com>
On Sun, Jul 06, 2014 at 08:39:53AM +0300, Michael S. Tsirkin wrote:
> On Fri, Jul 04, 2014 at 11:43:49AM +0200, Paolo Bonzini wrote:
> > After memory region QOMification QEMU is stricter in detecting
> > wrong usage of the memory region API. Here it detected a
> > memory_region_destroy done before the corresponding
> > memory_region_del_subregion; the memory_region_destroy is
> > done by msix_uninit_exclusive_bar, the memory_region_del_subregion
> > is done by the PCI core's pci_unregister_io_regions before
> > pc->exit is called.
> >
> > The misuse caused an assertion when hot-unplugging virtio
> > devices. Using the API correctly fixes the assertion.
> >
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Applied, thanks!
> I also added some historical context in the comments
> (the API misuse was introduced in 06a1307379fcd6c551185ad87679cd7ed896b9ea)
>
Fixed subject typo as well s/tree/free/
> > ---
> > hw/virtio/virtio-pci.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index 3c42cda..ecb2097 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -1003,11 +1003,9 @@ static void virtio_pci_device_plugged(DeviceState *d)
> >
> > static void virtio_pci_device_unplugged(DeviceState *d)
> > {
> > - PCIDevice *pci_dev = PCI_DEVICE(d);
> > VirtIOPCIProxy *proxy = VIRTIO_PCI(d);
> >
> > virtio_pci_stop_ioeventfd(proxy);
> > - msix_uninit_exclusive_bar(pci_dev);
> > }
> >
> > static int virtio_pci_init(PCIDevice *pci_dev)
> > @@ -1024,6 +1022,8 @@ static int virtio_pci_init(PCIDevice *pci_dev)
> > static void virtio_pci_exit(PCIDevice *pci_dev)
> > {
> > VirtIOPCIProxy *proxy = VIRTIO_PCI(pci_dev);
> > +
> > + msix_uninit_exclusive_bar(pci_dev);
> > memory_region_destroy(&proxy->bar);
> > }
> >
> > --
> > 1.9.3
prev parent reply other threads:[~2014-07-06 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 9:43 [Qemu-devel] [PATCH] virtio-pci: fix MSI memory region use after tree Paolo Bonzini
2014-07-06 5:39 ` Michael S. Tsirkin
2014-07-06 6:12 ` Michael S. Tsirkin [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=20140706061204.GA6461@redhat.com \
--to=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).