diff options
| author |   Baokun Li <libaokun1@huawei.com> | 2025-01-22 19:41:29 +0800 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2025-03-13 10:16:34 -0400 |
| commit | 6b76715d5e41fc332b0b879e66fad6ef3db07a3f (patch) | |
| tree | fe5b362b56153d61833f941b75e6bc2634b9e780 /scripts/lib/kdoc/kdoc_files.py | |
| parent | ext4: correct behavior under errors=remount-ro mode (diff) | |
| download | linux-rng-6b76715d5e41fc332b0b879e66fad6ef3db07a3f.tar.xz linux-rng-6b76715d5e41fc332b0b879e66fad6ef3db07a3f.zip | |
ext4: show 'emergency_ro' when EXT4_FLAGS_EMERGENCY_RO is set
After commit d3476f3dad4a ("ext4: don't set SB_RDONLY after filesystem
errors") in v6.12-rc1, the 'errors=remount-ro' mode no longer sets
SB_RDONLY on errors, which results in us seeing the filesystem is still
in rw state after errors.
Therefore, after setting EXT4_FLAGS_EMERGENCY_RO, display the emergency_ro
option so that users can query whether the current file system has become
emergency read-only due to errors through commands such as 'mount' or
'cat /proc/fs/ext4/sdx/options'.
Fixes: d3476f3dad4a ("ext4: don't set SB_RDONLY after filesystem errors")
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
Link: https://patch.msgid.link/20250122114130.229709-7-libaokun@huaweicloud.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions