ext4: don't try to modify s_flags if the the file system is read-only
authorTheodore Ts'o <tytso@mit.edu>
Wed, 12 Feb 2014 17:16:04 +0000 (12:16 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 7 Mar 2014 05:30:00 +0000 (21:30 -0800)
commitf13ea132887a8649cc6d45942e2be27f4362351f
tree880ff32e4f47c2693b8c2de58c60072fb964eb8c
parent4687eb1ebf2129cf46e636ec197173b99a4959e2
ext4: don't try to modify s_flags if the the file system is read-only

commit 23301410972330c0ae9a8afc379ba2005e249cc6 upstream.

If an ext4 file system is created by some tool other than mke2fs
(perhaps by someone who has a pathalogical fear of the GPL) that
doesn't set one or the other of the EXT2_FLAGS_{UN}SIGNED_HASH flags,
and that file system is then mounted read-only, don't try to modify
the s_flags field.  Otherwise, if dm_verity is in use, the superblock
will change, causing an dm_verity failure.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ext4/super.c