summaryrefslogtreecommitdiff
path: root/fs/btrfs/inode.c
diff options
context:
space:
mode:
authorLiu Bo <bo.li.liu@oracle.com>2018-01-25 11:02:51 -0700
committerDavid Sterba <dsterba@suse.com>2018-02-02 16:24:24 +0100
commit1846430c24d66e85cc58286b3319c82cd54debb2 (patch)
treea6bd680f201d90cc007254cb988093b41b936f8c /fs/btrfs/inode.c
parente89166990f11c3f21e1649d760dd35f9e410321c (diff)
downloadlinux-1846430c24d66e85cc58286b3319c82cd54debb2.tar.gz
linux-1846430c24d66e85cc58286b3319c82cd54debb2.tar.xz
Btrfs: fix crash due to not cleaning up tree log block's dirty bits
In cases that the whole fs flips into readonly status due to failures in critical sections, then log tree's blocks are still dirty, and this leads to a crash during umount time, the crash is about use-after-free, umount -> close_ctree -> stop workers -> iput(btree_inode) -> iput_final -> write_inode_now -> ... -> queue job on stop'd workers cc: <stable@vger.kernel.org> v3.12+ Fixes: 681ae50917df ("Btrfs: cleanup reserved space when freeing tree log on error") 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>
Diffstat (limited to 'fs/btrfs/inode.c')
0 files changed, 0 insertions, 0 deletions