Eric Biggers ba63f23d69 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>		2016-09-10 01:18:57 -04:00
..
crypto.c	block, fs, mm, drivers: use bio set/get op accessors	2016-06-07 13:41:38 -06:00
fname.c	Merge tag 'for-f2fs-4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs	2016-03-21 11:03:02 -07:00
Kconfig	fs crypto: move per-file encryption from f2fs tree to fs/crypto	2016-03-17 21:19:33 -07:00
keyinfo.c	fscrypto/f2fs: allow fs-specific key prefix for fs encryption	2016-05-07 10:32:33 -07:00
Makefile	fs crypto: move per-file encryption from f2fs tree to fs/crypto	2016-03-17 21:19:33 -07:00
policy.c	fscrypto: require write access to mount to set encryption policy	2016-09-10 01:18:57 -04:00