Eric Biggers 002ced4be6 fscrypto: only allow setting encryption policy on directories ... The FS_IOC_SET_ENCRYPTION_POLICY ioctl allowed setting an encryption policy on nondirectory files. This was unintentional, and in the case of nonempty regular files did not behave as expected because existing data was not actually encrypted by the ioctl. In the case of ext4, the user could also trigger filesystem errors in ->empty_dir(), e.g. due to mismatched "directory" checksums when the kernel incorrectly tried to interpret a regular file as a directory. This bug affected ext4 with kernels v4.8-rc1 or later and f2fs with kernels v4.6 and later. It appears that older kernels only permitted directories and that the check was accidentally lost during the refactoring to share the file encryption code between ext4 and f2fs. This patch restores the !S_ISDIR() check that was present in older kernels. Signed-off-by: Eric Biggers <ebiggers@google.com> Cc: stable@vger.kernel.org Signed-off-by: Theodore Ts'o <tytso@mit.edu>		2016-09-09 23:38:12 -04:00
..
crypto.c	block, fs, mm, drivers: use bio set/get op accessors	2016-06-07 13:41:38 -06:00
fname.c
Kconfig
keyinfo.c	fscrypto/f2fs: allow fs-specific key prefix for fs encryption	2016-05-07 10:32:33 -07:00
Makefile
policy.c	fscrypto: only allow setting encryption policy on directories	2016-09-09 23:38:12 -04:00