fscrypt: remove checks for encryption key after file open
Status from this message: Thanks, applied.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ext4: don't bother checking for encryption key in ->mmap()fs/ | +0 | 1 reply | |
| 2/4 | f2fs: don't bother checking for encryption key in ->mmap()fs/ | +0 | 1 reply | |
| 3/4 | ubifs: don't bother checking for encryption key in ->mmap()fs/ | +0 | 5 replies | |
| 4/4 | f2fs: don't bother checking for encryption key in ->write_iter()fs/ | +0 | 1 reply |
Reviews trailers per patch
3 of 4 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | David Gstir | Chao Yu | Richard Weinberger |
|---|---|---|---|
| Series | R-b | ||
| 1/4 | |||
| 2/4 | A-b | ||
| 3/4 | A-b | ||
| 4/4 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [PATCH 0/4] fscrypt: remove checks for encryption key after file open
From: Eric Biggers <[email protected]>
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(-)
Signature · 1 line
2.13.0.303.g4ebf302169-goog