fscrypt: use EEXIST when file already uses different policy
authorEric Biggers <ebiggers@google.com>
Mon, 5 Dec 2016 19:12:46 +0000 (11:12 -0800)
committerTheodore Ts'o <tytso@mit.edu>
Sat, 31 Dec 2016 21:26:20 +0000 (16:26 -0500)
commit8488cd96ff88966ccb076e4f3654f59d84ba686d
tree6e5ec746e22a9d57734e146092f81b57eb4fd984
parentdffd0cfa06d4ed83bb3ae8eb067989ceec5d18e1
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>
fs/crypto/policy.c