Whamcloud - gitweb
e2fsck: don't restart after a critical metadata collision in e2fsck -n mode
authorTheodore Ts'o <tytso@mit.edu>
Sun, 23 Jul 2017 04:08:18 +0000 (00:08 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 23 Jul 2017 04:44:25 +0000 (00:44 -0400)
commitf97c601a6c5b986586a5a39e5015c70e96c8bc9a
tree765aae8b0908f3a9aac9fffaf0a83afacec13d71
parent9c5b443c8e64cb5e1ea301d1c5e21980fcd986c8
e2fsck: don't restart after a critical metadata collision in e2fsck -n mode

If the file system isn't going to be changed, there's no point
restarting; it will just cause e2fsck to loop forever.

This problem was found using American Fuzzy Lop.

Reported-by: Adam Buchbinder <abuchbinder@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
e2fsck/pass1.c