From: Chao Yu <chao@kernel.org>
To: Eric Biggers <ebiggers3@gmail.com>, linux-fscrypt@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, Eric Biggers <ebiggers@google.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 2/4] f2fs: don't bother checking for encryption key in ->mmap()
Date: Tue, 23 May 2017 21:38:40 +0800 [thread overview]
Message-ID: <c38f38c1-7d74-d4a9-8b0a-51317fb20162@kernel.org> (raw)
In-Reply-To: <20170523003945.14279-3-ebiggers3@gmail.com>
On 2017/5/23 8:39, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Since only an open file can be mmap'ed, 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 mmap().
>
> This f2fs copy of 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@google.com>
Acked-by: Chao Yu <yuchao0@huawei.com>
Thanks,
> ---
> fs/f2fs/file.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 61af721329fa..ff4db3efc0ac 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -415,14 +415,6 @@ static int f2fs_file_mmap(struct file *file, struct vm_area_struct *vma)
> struct inode *inode = file_inode(file);
> int err;
>
> - if (f2fs_encrypted_inode(inode)) {
> - err = fscrypt_get_encryption_info(inode);
> - if (err)
> - return 0;
> - if (!f2fs_encrypted_inode(inode))
> - return -ENOKEY;
> - }
> -
> /* we don't need to use inline_data strictly */
> err = f2fs_convert_inline_inode(inode);
> if (err)
>
next prev parent reply other threads:[~2017-05-23 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:39 [PATCH 0/4] fscrypt: remove checks for encryption key after file open Eric Biggers
2017-05-23 0:39 ` [PATCH 1/4] ext4: don't bother checking for encryption key in ->mmap() Eric Biggers
2017-06-23 23:46 ` Theodore Ts'o
2017-05-23 0:39 ` [PATCH 2/4] f2fs: " Eric Biggers
2017-05-23 13:38 ` Chao Yu [this message]
2017-05-23 0:39 ` [PATCH 3/4] ubifs: " Eric Biggers
2017-05-23 14:14 ` Richard Weinberger
2017-06-23 16:09 ` Theodore Ts'o
2017-06-23 17:18 ` Eric Biggers
2017-06-23 17:20 ` Richard Weinberger
2017-06-23 17:28 ` Theodore Ts'o
2017-05-23 0:39 ` [PATCH 4/4] f2fs: don't bother checking for encryption key in ->write_iter() Eric Biggers
2017-05-23 13:39 ` Chao Yu
2017-05-23 5:56 ` [PATCH 0/4] fscrypt: remove checks for encryption key after file open David Gstir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c38f38c1-7d74-d4a9-8b0a-51317fb20162@kernel.org \
--to=chao@kernel.org \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).