]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
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>
Tue, 11 Mar 2014 23:09:56 +0000 (16:09 -0700)
commita8909f1fc06b034f0d790f48c8babf9bc6b2341f
tree9efad08c759c009838bc8a37e69b5e6edcf34989
parent2606524141e4ff9b6a5d0bcbd9d601dfc5a8285c
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