]> git.ipfire.org Git - people/arne_f/kernel.git/commit
ext4: avoid panic during forced reboot
authorJan Kara <jack@suse.cz>
Fri, 15 Mar 2019 03:46:05 +0000 (23:46 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 20 Apr 2019 07:16:45 +0000 (09:16 +0200)
commite239811047165d8ff4ccb9e1202bee49f25ef780
tree2a1e72070ff790db27d8fe627f1d3baf47a13cbe
parent0a7ef682097002cec926777228866149052e4751
ext4: avoid panic during forced reboot

[ Upstream commit 1dc1097ff60e4105216da7cd0aa99032b039a994 ]

When admin calls "reboot -f" - i.e., does a hard system reboot by
directly calling reboot(2) - ext4 filesystem mounted with errors=panic
can panic the system. This happens because the underlying device gets
disabled without unmounting the filesystem and thus some syscall running
in parallel to reboot(2) can result in the filesystem getting IO errors.

This is somewhat surprising to the users so try improve the behavior by
switching to errors=remount-ro behavior when the system is running
reboot(2).

Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/ext4/super.c