[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DA1CA888-856E-44A7-ABED-90F39D14C720@sigma-star.at>
Date: Tue, 23 May 2017 07:56:25 +0200
From: David Gstir <david@...ma-star.at>
To: Eric Biggers <ebiggers3@...il.com>
Cc: linux-fscrypt@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
Jaegeuk Kim <jaegeuk@...nel.org>, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org, Eric Biggers <ebiggers@...gle.com>
Subject: Re: [PATCH 0/4] fscrypt: remove checks for encryption key after file
open
Eric,
> On 23 May 2017, at 02:39, Eric Biggers <ebiggers3@...il.com> wrote:
>
> From: Eric Biggers <ebiggers@...gle.com>
>
> This series removes checks for a regular file's encryption key that occur
> after we've already opened the file. We're guaranteed to already have
> the key in such places, since we require it in ->open(). open() fails
> with ENOKEY otherwise, and a file descriptor is never made available.
>
> This pertains to regular files only. (Directories can be opened with or
> without their key.)
>
> Eric Biggers (4):
> ext4: don't bother checking for encryption key in ->mmap()
> f2fs: don't bother checking for encryption key in ->mmap()
> ubifs: don't bother checking for encryption key in ->mmap()
> f2fs: don't bother checking for encryption key in ->write_iter()
>
> fs/ext4/file.c | 7 -------
> fs/f2fs/file.c | 13 -------------
> fs/ubifs/file.c | 9 ---------
> 3 files changed, 29 deletions(-)
The whole series looks good to me. So feel free to add my
Reviewed-by: David Gstir <david@...ma-star.at>
David
Powered by blists - more mailing lists