diff options
| author | Eric Biggers <ebiggers@google.com> | 2016-09-09 00:20:38 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-10-27 11:23:18 +0300 |
| commit | 1bb1d4252d1ede47afea054979fb9d95fc891743 (patch) | |
| tree | 91902fba6512e6984b6baed007b1a069a62214a0 /fs/fscache | |
| parent | 8a004caec12bf241e567e3640401256cc9bc2e45 (diff) | |
| download | linux-1bb1d4252d1ede47afea054979fb9d95fc891743.tar.xz | |
fscrypto: require write access to mount to set encryption policy
commit ba63f23d69a3a10e7e527a02702023da68ef8a6d upstream.
[Please apply to 4.4-stable. Note: this was already backported, but
only to ext4; it was missed that it should go to f2fs as well. This is
needed to make xfstest generic/395 pass on f2fs.]
Since setting an encryption policy requires writing metadata to the
filesystem, it should be guarded by mnt_want_write/mnt_drop_write.
Otherwise, a user could cause a write to a frozen or readonly
filesystem. This was handled correctly by f2fs but not by ext4. Make
fscrypt_process_policy() handle it rather than relying on the filesystem
to get it right.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/fscache')
0 files changed, 0 insertions, 0 deletions