On Mon, Dec 05, 2016 at 11:12:44AM -0800, Eric Biggers wrote: > As part of an effort to clean up fscrypt-related error codes, make > attempting to create a file in an encrypted directory that hasn't been > "unlocked" fail with ENOKEY. Previously, several error codes were used > for this case, including ENOENT, EACCES, and EPERM, and they were not > consistent between and within filesystems. ENOKEY is a better choice > because it expresses that the failure is due to lacking the encryption > key. It also matches the error code returned when trying to open an > encrypted regular file without the key. > > I am not aware of any users who might be relying on the previous > inconsistent error codes, which were never documented anywhere. > > This failure case will be exercised by an xfstest. > > Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx> Applied to the fscrypt branch, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
