qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Li Qiang <liq3ea@gmail.com>
Cc: qemu-devel@nongnu.org, Li Qiang <liqiang6-s@360.cn>
Subject: Re: [Qemu-devel] [PATCH] 9pfs: fix memory leak in v9fs_xattrcreate
Date: Mon, 10 Oct 2016 13:20:51 +0200	[thread overview]
Message-ID: <20161010132051.7e1b3623@bahia> (raw)
In-Reply-To: <57fb706a.a8c8c20a.2886d.5bd5@mx.google.com>

On Mon, 10 Oct 2016 03:41:38 -0700
Li Qiang <liq3ea@gmail.com> wrote:

> From: Li Qiang <liqiang6-s@360.cn>
> 
> The 'fs.xattr.value' field in V9fsFidState object doesn't consider the
> situation that this field has been allocated previously. Every time, it
> will be allocated directly. This leads a host memory leak issue. This
> patch fix this.
> 
> Signed-off-by: Li Qiang <liqiang6-s@360.cn>
> ---

I'll add to the changelog that this may happen if the client sends a
Txattrcreate message with the same fid number before the fid was
clunked.

Reviewed-by: Greg Kurz <groug@kaod.org>

>  hw/9pfs/9p.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index 8751c19..e4040dc 100644
> --- a/hw/9pfs/9p.c
> +++ b/hw/9pfs/9p.c
> @@ -3282,6 +3282,7 @@ static void v9fs_xattrcreate(void *opaque)
>      xattr_fidp->fs.xattr.flags = flags;
>      v9fs_string_init(&xattr_fidp->fs.xattr.name);
>      v9fs_string_copy(&xattr_fidp->fs.xattr.name, &name);
> +    g_free(xattr_fidp->fs.xattr.value);
>      xattr_fidp->fs.xattr.value = g_malloc0(size);
>      err = offset;
>      put_fid(pdu, file_fidp);

  reply	other threads:[~2016-10-10 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 10:41 [Qemu-devel] [PATCH] 9pfs: fix memory leak in v9fs_xattrcreate Li Qiang
2016-10-10 11:20 ` Greg Kurz [this message]
2016-10-10 11:28   ` Greg Kurz
2016-10-10 11:54     ` Li Qiang
2016-10-10 12:08       ` 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=20161010132051.7e1b3623@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).