From: "Michael S. Tsirkin" <mst@redhat.com>
To: arei.gonglei@huawei.com
Cc: peter.crosthwaite@xilinx.com, weidong.huang@huawei.com,
qemu-stable@nongnu.org, luonengjun@huawei.com,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com,
imammedo@redhat.com, pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v5 0/4] Refactor device_set_realized to avoid resource leak.
Date: Tue, 2 Sep 2014 18:19:58 +0300 [thread overview]
Message-ID: <20140902151958.GA23192@redhat.com> (raw)
In-Reply-To: <1409659388-9404-1-git-send-email-arei.gonglei@huawei.com>
On Tue, Sep 02, 2014 at 08:03:04PM +0800, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
>
> after committing
> [PATCH v6 0/9] Refactor PCI/SHPC/PCIE hotplug to use a more generic hotplug API
Patches 1-3 make sense for qemu-stable?
Andreas could you please comment and if yes pick them
up and add Cc qemu-stable?
2.1.1 freeze is tomorrow.
> If devcie hotplugging failed, will casuse resource leak.
> This patch series include address resouce leak and two other issuses.
>
> v5 -> v4:
> - add patch 1/4 'Reviewed-by' tag.
> - change patch 2/4, propagate firsh child unrealizing failure, and
> change this patch's commit message.(Peter)
>
> v4 -> v3:
> - add patch 2/4.(Thanks for Peter's suggestion)
> - rework patch 3/4 based on patch 2/4.
>
> v3 -> v2:
> - add cleanup logic for set bus/child_bus realized/unrealized failed.
> - change patch 1/3 commit message, add 'Reviewed-by' tag.
>
> v2 -> v1:
> - rewrite patch 1/3, using error_abort instead of local_err.
> - rewrite patch 2/3, add cleanup logic for different error embranchment.
> - rewrite title of patch 3/3, and a syntax fix.
>
> Gonglei (4):
> qdev: using error_abort instead of using local_err
> qdev: using NULL instead of local_err for qbus_child unrealize
> qdev: add cleanup logic in device_set_realized() to avoid resource
> leak
> pcie: don't assert when hotplug a PCIe device with 'function != 0'
>
> hw/core/qdev.c | 69 +++++++++++++++++++++++++++++++++++++++++++---------------
> hw/pci/pcie.c | 6 ++++-
> 2 files changed, 56 insertions(+), 19 deletions(-)
>
> --
> 1.7.12.4
>
prev parent reply other threads:[~2014-09-02 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 12:03 [Qemu-devel] [PATCH v5 0/4] Refactor device_set_realized to avoid resource leak arei.gonglei
2014-09-02 12:03 ` [Qemu-devel] [PATCH v5 1/4] qdev: using error_abort instead of using local_err arei.gonglei
2014-09-03 14:29 ` Andreas Färber
2014-09-04 1:03 ` Gonglei (Arei)
2014-09-02 12:03 ` [Qemu-devel] [PATCH v5 2/4] qdev: using NULL instead of local_err for qbus_child unrealize arei.gonglei
2014-09-03 13:08 ` Peter Crosthwaite
2014-09-04 0:58 ` Gonglei (Arei)
2014-09-02 12:03 ` [Qemu-devel] [PATCH v5 3/4] qdev: add cleanup logic in device_set_realized() to avoid resource leak arei.gonglei
2014-09-03 13:08 ` Peter Crosthwaite
2014-09-02 12:03 ` [Qemu-devel] [PATCH v5 4/4] pcie: don't assert when hotplug a PCIe device with 'function != 0' arei.gonglei
2014-09-03 13:48 ` Michael S. Tsirkin
2014-09-04 0:25 ` Gonglei (Arei)
2014-09-02 15:19 ` 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=20140902151958.GA23192@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=imammedo@redhat.com \
--cc=luonengjun@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=weidong.huang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.