Btrfs: fix extent state leak from tree log
authorLiu Bo <bo.li.liu@oracle.com>
Thu, 25 Jan 2018 18:02:52 +0000 (11:02 -0700)
committerDavid Sterba <dsterba@suse.com>
Fri, 2 Feb 2018 15:24:30 +0000 (16:24 +0100)
commit55237a5f2431a72435e3ed39e4306e973c0446b7
tree6328003f97e70a6afc45872cd64e0ac5bc987c24
parent1846430c24d66e85cc58286b3319c82cd54debb2
Btrfs: fix extent state leak from tree log

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>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/tree-log.c