Liu Bo af72273381 Btrfs: clean up resources during umount after trans is aborted
Currently if some fatal errors occur, like all IO get -EIO, resources
would be cleaned up when
a) transaction is being committed or
b) BTRFS_FS_STATE_ERROR is set

However, in some rare cases, resources may be left alone after transaction
gets aborted and umount may run into some ASSERT(), e.g.
ASSERT(list_empty(&block_group->dirty_list));

For case a), in btrfs_commit_transaciton(), there're several places at the
beginning where we just call btrfs_end_transaction() without cleaning up
resources.  For case b), it is possible that the trans handle doesn't have
any dirty stuff, then only trans hanlde is marked as aborted while
BTRFS_FS_STATE_ERROR is not set, so resources remain in memory.

This makes btrfs also check BTRFS_FS_STATE_TRANS_ABORTED to make sure that
all resources won't stay in memory after umount.

Signed-off-by: Liu Bo <bo.liu@linux.alibaba.com>
Signed-off-by: David Sterba <dsterba@suse.com>
2018-04-12 14:49:47 +02:00
..
2018-02-06 14:43:37 +00:00
2018-02-07 14:25:22 -08:00
2018-02-07 14:25:22 -08:00
2017-11-16 11:41:22 -08:00
2018-01-24 17:33:57 -05:00
2018-02-06 18:32:45 -08:00
2018-01-01 10:09:33 -05:00
2018-03-07 11:47:15 +01:00
2018-02-07 14:25:22 -08:00
2018-02-06 18:32:45 -08:00
2018-01-03 10:13:36 -08:00
2017-12-07 14:23:30 -05:00
2018-01-29 07:27:24 -08:00
2018-02-06 10:41:33 -08:00
2018-02-08 15:18:32 -08:00
2017-12-09 20:16:33 -05:00