diff options
| author | Eric Biggers <ebiggers@google.com> | 2016-09-08 23:20:38 +0200 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2016-09-10 07:18:57 +0200 |
| commit | ba63f23d69a3a10e7e527a02702023da68ef8a6d (patch) | |
| tree | ef70ece0179f4d642e0b0b4d5f6aa6cfed7c9e74 /ipc | |
| parent | fscrypto: only allow setting encryption policy on directories (diff) | |
| download | linux-ba63f23d69a3a10e7e527a02702023da68ef8a6d.tar.xz linux-ba63f23d69a3a10e7e527a02702023da68ef8a6d.zip | |
fscrypto: require write access to mount to set encryption policy
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>
Cc: stable@vger.kernel.org # 4.1+; check fs/{ext4,f2fs}
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions