All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix memory leak in do_walk_down
Date: Thu, 22 Sep 2016 10:57:58 -0700	[thread overview]
Message-ID: <20160922175753.GA12906@localhost.localdomain> (raw)
In-Reply-To: <20160922151025.GQ16983@twin.jikos.cz>

On Thu, Sep 22, 2016 at 05:10:25PM +0200, David Sterba wrote:
> On Tue, Sep 13, 2016 at 07:02:27PM -0700, Liu Bo wrote:
> > The extent buffer 'next' needs to be free'd conditionally.
> > 
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> 
> Reviewed-by: David Sterba <dsterba@suse.com>
> 
> Josef's patch contained this fix but mixed with other (removing BUG_ON).
> I've removed it so we can merge both patches, for sake of better change
> separation.

Good to know that, thank you for the efforts.

Thanks,

-liubo

      reply	other threads:[~2016-09-22 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  2:02 [PATCH] Btrfs: fix memory leak in do_walk_down Liu Bo
2016-09-14 13:19 ` Holger Hoffstätte
2016-09-22 15:01   ` David Sterba
2016-09-22 15:10 ` David Sterba
2016-09-22 17:57   ` Liu Bo [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=20160922175753.GA12906@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.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.