From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [GIT PULL] fscrypt updates for 5.18
Date: Sun, 20 Mar 2022 21:50:19 -0700 [thread overview]
Message-ID: <YjgEC8Nw9PDmdY0O@sol.localdomain> (raw)
The following changes since commit dfd42facf1e4ada021b939b4e19c935dcdd55566:
Linux 5.17-rc3 (2022-02-06 12:20:50 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus
for you to fetch changes up to cdaa1b1941f667814300799ddb74f3079517cd5a:
fscrypt: update documentation for direct I/O support (2022-02-08 11:02:18 -0800)
----------------------------------------------------------------
Add support for direct I/O on encrypted files when blk-crypto (inline
encryption) is being used for file contents encryption.
There will be a merge conflict with the block pull request in
fs/iomap/direct-io.c, due to some bio interface cleanups. The merge
resolution is straightforward and can be found in linux-next.
----------------------------------------------------------------
Eric Biggers (5):
fscrypt: add functions for direct I/O support
iomap: support direct I/O with fscrypt using blk-crypto
ext4: support direct I/O with fscrypt using blk-crypto
f2fs: support direct I/O with fscrypt using blk-crypto
fscrypt: update documentation for direct I/O support
Documentation/filesystems/fscrypt.rst | 25 +++++++++-
fs/crypto/crypto.c | 8 +++
fs/crypto/inline_crypt.c | 93 +++++++++++++++++++++++++++++++++++
fs/ext4/file.c | 10 ++--
fs/ext4/inode.c | 7 +++
fs/f2fs/data.c | 7 +++
fs/f2fs/f2fs.h | 6 ++-
fs/iomap/direct-io.c | 6 +++
include/linux/fscrypt.h | 18 +++++++
9 files changed, 173 insertions(+), 7 deletions(-)
next reply other threads:[~2022-03-21 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 4:50 Eric Biggers [this message]
2022-03-22 18:31 ` [GIT PULL] fscrypt updates for 5.18 pr-tracker-bot
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=YjgEC8Nw9PDmdY0O@sol.localdomain \
--to=ebiggers@kernel.org \
--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-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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