ext4: avoid panic during forced reboot
authorJan Kara <jack@suse.cz>
Fri, 15 Mar 2019 03:46:05 +0000 (23:46 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 15 Mar 2019 03:46:05 +0000 (23:46 -0400)
commit1dc1097ff60e4105216da7cd0aa99032b039a994
tree4fc2321b1a4cae5ed6f34228cd2c04bf217efd32
parent372a03e01853f860560eade508794dd274e9b390
ext4: avoid panic during forced reboot

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>
fs/ext4/super.c