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 2/2] 9pfs: fix memory leak about xattr value
Date: Mon, 10 Oct 2016 11:06:11 +0200 [thread overview]
Message-ID: <20161010110611.385ef476@bahia> (raw)
In-Reply-To: <648301670b2dc88aec68e48abd1bef07c1e201a3.1475990063.git.liqiang6-s@360.cn>
On Sat, 8 Oct 2016 22:27:08 -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.
>
This cannot happen because v9fs_xattrwalk() always allocates this fid:
xattr_fidp = alloc_fid(s, newfid);
if (xattr_fidp == NULL) {
err = -EINVAL;
goto out;
}
> Signed-off-by: Li Qiang <liqiang6-s@360.cn>
> ---
> hw/9pfs/9p.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index 8751c19..3af23f9 100644
> --- a/hw/9pfs/9p.c
> +++ b/hw/9pfs/9p.c
> @@ -350,6 +350,7 @@ free_out:
> v9fs_string_free(&fidp->fs.xattr.name);
> free_value:
> g_free(fidp->fs.xattr.value);
> + fidp->fs.xattr.value = NULL;
> return retval;
> }
>
> @@ -3191,7 +3192,8 @@ static void v9fs_xattrwalk(void *opaque)
> xattr_fidp->fid_type = P9_FID_XATTR;
> xattr_fidp->fs.xattr.copied_len = -1;
> if (size) {
> - xattr_fidp->fs.xattr.value = g_malloc(size);
> + xattr_fidp->fs.xattr.value = g_realloc(
> + xattr_fidp->fs.xattr.value, size);
> err = v9fs_co_llistxattr(pdu, &xattr_fidp->path,
> xattr_fidp->fs.xattr.value,
> xattr_fidp->fs.xattr.len);
> @@ -3224,7 +3226,8 @@ static void v9fs_xattrwalk(void *opaque)
> xattr_fidp->fid_type = P9_FID_XATTR;
> xattr_fidp->fs.xattr.copied_len = -1;
> if (size) {
> - xattr_fidp->fs.xattr.value = g_malloc(size);
> + xattr_fidp->fs.xattr.value = g_realloc(
> + xattr_fidp->fs.xattr.value, size);
> err = v9fs_co_lgetxattr(pdu, &xattr_fidp->path,
> &name, xattr_fidp->fs.xattr.value,
> xattr_fidp->fs.xattr.len);
next prev parent reply other threads:[~2016-10-10 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 5:25 [Qemu-devel] [PATCH 0/2] 9pfs: fix xattr issues Li Qiang
2016-10-09 5:26 ` [Qemu-devel] [PATCH 1/2] 9pfs: fix information leak in xattr read Li Qiang
2016-10-10 8:56 ` Greg Kurz
2016-10-12 13:23 ` Greg Kurz
2016-10-12 20:49 ` Eric Blake
2016-10-13 3:30 ` Li Qiang
2016-10-13 8:08 ` Greg Kurz
2016-10-13 7:51 ` Greg Kurz
2016-10-09 5:27 ` [Qemu-devel] [PATCH 2/2] 9pfs: fix memory leak about xattr value Li Qiang
2016-10-10 9:06 ` Greg Kurz [this message]
2016-10-10 9:15 ` Li Qiang
2016-10-10 10:21 ` 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=20161010110611.385ef476@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.