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.5
Date: Sun, 24 Nov 2019 20:41:22 -0800 [thread overview]
Message-ID: <20191125044122.GA9817@sol.localdomain> (raw)
The following changes since commit 7d194c2100ad2a6dded545887d02754948ca5241:
Linux 5.4-rc4 (2019-10-20 15:56:22 -0400)
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 0eee17e3322625b87ce5fa631bda16562a8dc494:
f2fs: add support for IV_INO_LBLK_64 encryption policies (2019-11-06 12:34:42 -0800)
----------------------------------------------------------------
- Add the IV_INO_LBLK_64 encryption policy flag which modifies the
encryption to be optimized for UFS inline encryption hardware.
- For AES-128-CBC, use the crypto API's implementation of ESSIV (which
was added in 5.4) rather than doing ESSIV manually.
- A few other cleanups.
----------------------------------------------------------------
Eric Biggers (8):
fscrypt: invoke crypto API for ESSIV handling
fscrypt: remove struct fscrypt_ctx
fscrypt: zeroize fscrypt_info before freeing
docs: ioctl-number: document fscrypt ioctl numbers
fscrypt: avoid data race on fscrypt_mode::logged_impl_name
fscrypt: add support for IV_INO_LBLK_64 policies
ext4: add support for IV_INO_LBLK_64 encryption policies
f2fs: add support for IV_INO_LBLK_64 encryption policies
Documentation/filesystems/fscrypt.rst | 68 +++++++++------
Documentation/ioctl/ioctl-number.rst | 1 +
fs/crypto/bio.c | 29 +------
fs/crypto/crypto.c | 124 ++++----------------------
fs/crypto/fscrypt_private.h | 25 +++---
fs/crypto/keyring.c | 6 +-
fs/crypto/keysetup.c | 158 ++++++++++------------------------
fs/crypto/keysetup_v1.c | 4 -
fs/crypto/policy.c | 41 ++++++++-
fs/ext4/ext4.h | 2 +
fs/ext4/super.c | 14 +++
fs/f2fs/super.c | 26 ++++--
include/linux/fscrypt.h | 35 +-------
include/uapi/linux/fscrypt.h | 3 +-
14 files changed, 208 insertions(+), 328 deletions(-)
next reply other threads:[~2019-11-25 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 4:41 Eric Biggers [this message]
2019-11-25 22:45 ` [GIT PULL] fscrypt updates for 5.5 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=20191125044122.GA9817@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;
as well as URLs for NNTP newsgroup(s).