diff options
| author | Eric Biggers <ebiggers@google.com> | 2017-06-13 16:47:54 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2017-07-04 02:11:46 -0700 |
| commit | 67773a1fbdcb5be4a0490b1dd2a5975784ef40df (patch) | |
| tree | ce3d823e454f55d2c638e99d0a12ccd63469fbf0 /fs/f2fs | |
| parent | 8ceffcb29e61ba882a011b1e4d73ca03691fdc2e (diff) | |
| download | linux-stable-67773a1fbdcb5be4a0490b1dd2a5975784ef40df.tar.gz linux-stable-67773a1fbdcb5be4a0490b1dd2a5975784ef40df.tar.bz2 linux-stable-67773a1fbdcb5be4a0490b1dd2a5975784ef40df.zip | |
f2fs: require key for truncate(2) of encrypted file
Currently, filesystems allow truncate(2) on an encrypted file without
the encryption key. However, it's impossible to correctly handle the
case where the size being truncated to is not a multiple of the
filesystem block size, because that would require decrypting the final
block, zeroing the part beyond i_size, then encrypting the block.
As other modifications to encrypted file contents are prohibited without
the key, just prohibit truncate(2) as well, making it fail with ENOKEY.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Acked-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs')
| -rw-r--r-- | fs/f2fs/file.c | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index ac8b943817e6..61ee029d7e48 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -710,9 +710,13 @@ int f2fs_setattr(struct dentry *dentry, struct iattr *attr) return err; if (attr->ia_valid & ATTR_SIZE) { - if (f2fs_encrypted_inode(inode) && - fscrypt_get_encryption_info(inode)) - return -EACCES; + if (f2fs_encrypted_inode(inode)) { + err = fscrypt_get_encryption_info(inode); + if (err) + return err; + if (!fscrypt_has_encryption_key(inode)) + return -ENOKEY; + } if (attr->ia_size <= i_size_read(inode)) { down_write(&F2FS_I(inode)->i_mmap_sem); |