diff options
| author | Jan Kara <jack@suse.cz> | 2024-10-05 00:15:56 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-12-05 14:01:12 +0100 |
| commit | 26cc5063e3c2a5d14f42fe623c9567bd1499fb19 (patch) | |
| tree | 4c1eace83cd9685b5e47675b2b30fc0be18852ce /scripts/const_structs.checkpatch | |
| parent | 63dfd728b30f79495dacc886127695a379805152 (diff) | |
| download | linux-26cc5063e3c2a5d14f42fe623c9567bd1499fb19.tar.gz linux-26cc5063e3c2a5d14f42fe623c9567bd1499fb19.tar.bz2 linux-26cc5063e3c2a5d14f42fe623c9567bd1499fb19.zip | |
ext4: avoid remount errors with 'abort' mount option
[ Upstream commit 76486b104168ae59703190566e372badf433314b ]
When we remount filesystem with 'abort' mount option while changing
other mount options as well (as is LTP test doing), we can return error
from the system call after commit d3476f3dad4a ("ext4: don't set
SB_RDONLY after filesystem errors") because the application of mount
option changes detects shutdown filesystem and refuses to do anything.
The behavior of application of other mount options in presence of
'abort' mount option is currently rather arbitary as some mount option
changes are handled before 'abort' and some after it.
Move aborting of the filesystem to the end of remount handling so all
requested changes are properly applied before the filesystem is shutdown
to have a reasonably consistent behavior.
Fixes: d3476f3dad4a ("ext4: don't set SB_RDONLY after filesystem errors")
Reported-by: Jan Stancek <jstancek@redhat.com>
Link: https://lore.kernel.org/all/Zvp6L+oFnfASaoHl@t14s
Signed-off-by: Jan Kara <jack@suse.cz>
Tested-by: Jan Stancek <jstancek@redhat.com>
Link: https://patch.msgid.link/20241004221556.19222-1-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions