summaryrefslogtreecommitdiff
path: root/fs/lockd
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2023-06-16 18:50:51 +0200
committerTheodore Ts'o <tytso@mit.edu>2023-07-29 18:37:53 -0400
commit95257987a6387f02970eda707e55a06cce734e18 (patch)
tree6aebb66d674a8d511c465415376e9026dc087bdb /fs/lockd
parent22b8d707b07e6e06f50fe1d9ca8756e1f894eb0d (diff)
downloadlwn-95257987a6387f02970eda707e55a06cce734e18.tar.gz
lwn-95257987a6387f02970eda707e55a06cce734e18.zip
ext4: drop EXT4_MF_FS_ABORTED flag
EXT4_MF_FS_ABORTED flag has practically the same intent as EXT4_FLAGS_SHUTDOWN flag. The shutdown flag is checked in many more places than the aborted flag which is mostly the historical artifact where we were relying on SB_RDONLY checks instead of the aborted flag checks. There are only three places - ext4_sync_file(), __ext4_remount(), and mballoc debug code - which check aborted flag and not shutdown flag and this is arguably a bug. Avoid these inconsistencies by removing EXT4_MF_FS_ABORTED flag and using EXT4_FLAGS_SHUTDOWN everywhere. Signed-off-by: Jan Kara <jack@suse.cz> Link: https://lore.kernel.org/r/20230616165109.21695-5-jack@suse.cz Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/lockd')
0 files changed, 0 insertions, 0 deletions