All of lore.kernel.org
 help / color / mirror / Atom feed
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 1/3] 9pfs: add cleanup operation in FileOperations
Date: Mon, 14 Nov 2016 18:32:26 +0100	[thread overview]
Message-ID: <20161114183226.0f3d4461@bahia> (raw)
In-Reply-To: <5829af0b.84f4420a.a436f.4a6d@mx.google.com>

On Mon, 14 Nov 2016 07:32:56 -0500
Li Qiang <liq3ea@gmail.com> wrote:

> From: Li Qiang <liq3ea@gmail.com>
> 
> Currently, the backend of VirtFS doesn't have a cleanup
> function. This will lead resource leak issues if the backed
> driver allocates resources. This patch addresses this issue.
> 
> Signed-off-by: Li Qiang <liq3ea@gmail.com>
> ---
>  fsdev/file-op-9p.h | 1 +
>  hw/9pfs/9p.c       | 3 +++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/fsdev/file-op-9p.h b/fsdev/file-op-9p.h
> index 6db9fea..a56dc84 100644
> --- a/fsdev/file-op-9p.h
> +++ b/fsdev/file-op-9p.h
> @@ -100,6 +100,7 @@ struct FileOperations
>  {
>      int (*parse_opts)(QemuOpts *, struct FsDriverEntry *);
>      int (*init)(struct FsContext *);
> +    void (*cleanup)(struct FsContext *);
>      int (*lstat)(FsContext *, V9fsPath *, struct stat *);
>      ssize_t (*readlink)(FsContext *, V9fsPath *, char *, size_t);
>      int (*chmod)(FsContext *, V9fsPath *, FsCred *);
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index aea7e9d..166b5a7 100644
> --- a/hw/9pfs/9p.c
> +++ b/hw/9pfs/9p.c
> @@ -3532,6 +3532,9 @@ void v9fs_device_unrealize_common(V9fsState *s, Error **errp)
>  {
>      g_free(s->ctx.fs_root);
>      g_free(s->tag);
> +    if (s->ops->cleanup) {
> +        s->ops->cleanup(&s->ctx);
> +    }

Unrealize should undo things that were set during realize in reverse order: 
please move the cleanup stuff above calls to g_free() (which are actually
misordered since tag is allocated after fs_root... maybe you can fix that
too in a preparatory patch).

You also have to call cleanup in the error path of realize if init was
called.

>  }
>  
>  typedef struct VirtfsCoResetData {

  reply	other threads:[~2016-11-14 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1479126778-125867-1-git-send-email-Qiang(liqiang6-s@360.cn)>
2016-11-14 12:32 ` [Qemu-devel] [PATCH 1/3] 9pfs: add cleanup operation in FileOperations Li Qiang
2016-11-14 17:32   ` Greg Kurz [this message]
2016-11-14 12:32 ` [Qemu-devel] [PATCH 2/3] 9pfs: add cleanup operation for handle backend driver Li Qiang
2016-11-14 17:36   ` Greg Kurz
2016-11-14 12:32 ` [Qemu-devel] [PATCH 3/3] 9pfs: add cleanup operation for proxy " Li Qiang
2016-11-14 17:36   ` Greg Kurz

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=20161114183226.0f3d4461@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 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.