On Mon, Dec 19, 2016 at 02:20:13PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@xxxxxxxxxx>
>
> Attempting to link a device node, named pipe, or socket file into an
> encrypted directory through rename(2) or link(2) always failed with
> EPERM. This happened because fscrypt_has_permitted_context() saw that
> the file was unencrypted and forbid creating the link. This behavior
> was unexpected because such files are never encrypted; only regular
> files, directories, and symlinks can be encrypted.
>
> To fix this, make fscrypt_has_permitted_context() always return true on
> special files.
>
> This will be covered by a test in my encryption xfstests patchset.
>
> Fixes: 9bd8212f981e ("ext4 crypto: add encryption policy and password salt support")
> Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx>
> Reviewed-by: Richard Weinberger <richard@xxxxxx>
> Cc: stable@xxxxxxxxxxxxxxx
Thanks, applied.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
