Eric Biggers 8488cd96ff fscrypt: use EEXIST when file already uses different policy ... As part of an effort to clean up fscrypt-related error codes, make FS_IOC_SET_ENCRYPTION_POLICY fail with EEXIST when the file already uses a different encryption policy. This is more descriptive than EINVAL, which was ambiguous with some of the other error cases. I am not aware of any users who might be relying on the previous error code of EINVAL, which was never documented anywhere. This failure case will be exercised by an xfstest. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>		2016-12-31 16:26:20 -05:00
..
crypto.c	fscrypt: Rename FS_WRITE_PATH_FL to FS_CTX_HAS_BOUNCE_BUFFER_FL	2016-12-11 16:33:18 -05:00
fname.c	fscrypt: use ENOKEY when file cannot be created w/o key	2016-12-31 16:26:20 -05:00
fscrypt_private.h	fscrypt: Rename FS_WRITE_PATH_FL to FS_CTX_HAS_BOUNCE_BUFFER_FL	2016-12-11 16:33:18 -05:00
Kconfig	fscrypto: remove unneeded Kconfig dependencies	2016-12-11 16:26:07 -05:00
keyinfo.c	fscrypt: fix the test_dummy_encryption mount option	2016-12-27 19:46:27 -05:00
Makefile	fs crypto: move per-file encryption from f2fs tree to fs/crypto	2016-03-17 21:19:33 -07:00
policy.c	fscrypt: use EEXIST when file already uses different policy	2016-12-31 16:26:20 -05:00