From: Greg Kurz <groug@kaod.org>
To: Li Qiang <liq3ea@gmail.com>
Cc: qemu-devel@nongnu.org, liqiang6-s@360.cn
Subject: Re: [Qemu-devel] [PATCH v3 0/4] 9pfs: add cleanup operation in handle/proxy backend
Date: Mon, 21 Nov 2016 17:05:02 +0100 [thread overview]
Message-ID: <20161121170502.4ab9d813@bahia> (raw)
In-Reply-To: <1479352616-64991-1-git-send-email-liq3ea@gmail.com>
On Wed, 16 Nov 2016 22:16:52 -0500
Li Qiang <liq3ea@gmail.com> wrote:
> Currently, the backend of VirtFS doesn't have a cleanup
> function. This will leak some resources in handle and proxy
> backend driver. This patchset addresses this issue.
>
> Li Qiang (4):
> 9pfs: adjust the order of resource cleanup in device unrealize
> 9pfs: add cleanup operation in FileOperations
> 9pfs: add cleanup operation for handle backend driver
> 9pfs: add cleanup operation for proxy backend driver
>
> fsdev/file-op-9p.h | 1 +
> hw/9pfs/9p-handle.c | 9 +++++++++
> hw/9pfs/9p-proxy.c | 13 +++++++++++++
> hw/9pfs/9p.c | 10 ++++++++--
> 4 files changed, 31 insertions(+), 2 deletions(-)
>
Hi Li,
This looks good. I'll send a pull request shortly.
Thanks for your help in fixing all these leaks.
--
Greg
prev parent reply other threads:[~2016-11-21 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 3:16 [Qemu-devel] [PATCH v3 0/4] 9pfs: add cleanup operation in handle/proxy backend Li Qiang
2016-11-17 3:16 ` [Qemu-devel] [PATCH v3 1/4] 9pfs: adjust the order of resource cleanup in device unrealize Li Qiang
2016-11-17 3:16 ` [Qemu-devel] [PATCH v3 2/4] 9pfs: add cleanup operation in FileOperations Li Qiang
2016-11-17 3:16 ` [Qemu-devel] [PATCH v3 3/4] 9pfs: add cleanup operation for handle backend driver Li Qiang
2016-11-17 3:16 ` [Qemu-devel] [PATCH v3 4/4] 9pfs: add cleanup operation for proxy " Li Qiang
2016-11-21 16:05 ` Greg Kurz [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=20161121170502.4ab9d813@bahia \
--to=groug@kaod.org \
--cc=liq3ea@gmail.com \
--cc=liqiang6-s@360.cn \
--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).