From: Josef Bacik <josef@toxicpanda.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix extent state leak from tree log
Date: Fri, 26 Jan 2018 09:05:20 -0500 [thread overview]
Message-ID: <20180126140520.3cyb53ttwayadqu6@destiny> (raw)
In-Reply-To: <20180125180256.10844-5-bo.li.liu@oracle.com>
On Thu, Jan 25, 2018 at 11:02:52AM -0700, Liu Bo wrote:
> It's possible that btrfs_sync_log() bails out after one of the two
> btrfs_write_marked_extents() which convert extent state's state bit into
> EXTENT_NEED_WAIT from EXTENT_DIRTY/EXTENT_NEW, however only EXTENT_DIRTY
> and EXTENT_NEW are searched by free_log_tree() so that those extent states
> with EXTENT_NEED_WAIT lead to memory leak.
>
> cc: <stable@vger.kernel.org>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Thanks,
Josef
prev parent reply other threads:[~2018-01-26 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 18:02 [PATCH] Btrfs: fix extent state leak from tree log Liu Bo
2018-01-26 14:05 ` Josef Bacik [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=20180126140520.3cyb53ttwayadqu6@destiny \
--to=josef@toxicpanda.com \
--cc=bo.li.liu@oracle.com \
--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 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).