[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6016f168-9c2b-e7a6-4d21-9b40c4cb6edc@kernel.org>
Date: Tue, 23 May 2017 21:39:13 +0800
From: Chao Yu <chao@...nel.org>
To: Eric Biggers <ebiggers3@...il.com>, linux-fscrypt@...r.kernel.org
Cc: Theodore Ts'o <tytso@....edu>, Eric Biggers <ebiggers@...gle.com>,
linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org, Jaegeuk Kim <jaegeuk@...nel.org>,
linux-ext4@...r.kernel.org
Subject: Re: [f2fs-dev] [PATCH 4/4] f2fs: don't bother checking for encryption
key in ->write_iter()
On 2017/5/23 8:39, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> Since only an open file can be written to, and we only allow open()ing
> an encrypted file when its key is available, there is no need to check
> for the key again before permitting each ->write_iter().
>
> This code was also broken in that it wouldn't actually have failed if
> the key was in fact unavailable.
>
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
Acked-by: Chao Yu <yuchao0@...wei.com>
Thanks,
> ---
> fs/f2fs/file.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index ff4db3efc0ac..3ccc63089a47 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -2318,11 +2318,6 @@ static ssize_t f2fs_file_write_iter(struct kiocb *iocb, struct iov_iter *from)
> struct blk_plug plug;
> ssize_t ret;
>
> - if (f2fs_encrypted_inode(inode) &&
> - !fscrypt_has_encryption_key(inode) &&
> - fscrypt_get_encryption_info(inode))
> - return -EACCES;
> -
> inode_lock(inode);
> ret = generic_write_checks(iocb, from);
> if (ret > 0) {
>
Powered by blists - more mailing lists