qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org, "Yan Wang" <wangyan122@huawei.com>
Subject: Re: [PATCH] 9p: local: fix memory leak
Date: Mon, 6 Jan 2020 11:54:25 +0100	[thread overview]
Message-ID: <20200106115425.1ef819d8@bahia.lan> (raw)
In-Reply-To: <1582630.xPu3mGmscH@silver>

On Mon, 30 Dec 2019 12:34:51 +0100
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:

> On Montag, 30. Dezember 2019 03:23:47 CET Yan Wang wrote:
> > Signed-off-by: Yan Wang <wangyan122@huawei.com>
> > ---
> >  hw/9pfs/9p-local.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/hw/9pfs/9p-local.c b/hw/9pfs/9p-local.c
> > index ca641390fb..d0592c3b45 100644
> > --- a/hw/9pfs/9p-local.c
> > +++ b/hw/9pfs/9p-local.c
> > @@ -947,7 +947,7 @@ static int local_link(FsContext *ctx, V9fsPath *oldpath,
> > if (ctx->export_flags & V9FS_SM_MAPPED_FILE &&
> >          local_is_mapped_file_metadata(ctx, name)) {
> >          errno = EINVAL;
> > -        return -1;
> > +        goto out;
> >      }
> > 
> >      odirfd = local_opendir_nofollow(ctx, odirpath);
> 
> This issue was already addressed 10 days ago and is scheduled for merge on 
> Greg's 9p-next branch:
> 
> https://github.com/gkurz/qemu/commit/ac5987075f42e44419a461846fdefde8ab4dd624
> 
> https://lists.gnu.org/archive/html/qemu-devel/2019-12/msg04774.html
> 
> 

That's correct.

Philippe,

If the commit description meets your expectations, just tell me and
I'll add your R-b.

Cheers and happy new year,

--
Greg


      reply	other threads:[~2020-01-06 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30  2:23 [PATCH] 9p: local: fix memory leak Yan Wang
2019-12-30  8:35 ` Philippe Mathieu-Daudé
2019-12-30 11:34 ` Christian Schoenebeck
2020-01-06 10:54   ` 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=20200106115425.1ef819d8@bahia.lan \
    --to=groug@kaod.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu_oss@crudebyte.com \
    --cc=wangyan122@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 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).