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-mtd@lists.infradead.org, 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.16
Date: Sun, 31 Oct 2021 16:15:02 -0700 [thread overview]
Message-ID: <YX8jdp73zUDwlB5E@sol.localdomain> (raw)
The following changes since commit e4e737bb5c170df6135a127739a9e6148ee3da82:
Linux 5.15-rc2 (2021-09-19 17:28:22 -0700)
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 b7e072f9b77f4c516df96e0c22ec09f8b2e76ba1:
fscrypt: improve a few comments (2021-10-25 19:11:50 -0700)
----------------------------------------------------------------
Some cleanups for fs/crypto/:
- Allow 256-bit master keys with AES-256-XTS
- Improve documentation and comments
- Remove unneeded field fscrypt_operations::max_namelen
----------------------------------------------------------------
Eric Biggers (5):
fscrypt: remove fscrypt_operations::max_namelen
fscrypt: clean up comments in bio.c
fscrypt: improve documentation for inline encryption
fscrypt: allow 256-bit master keys with AES-256-XTS
fscrypt: improve a few comments
Documentation/block/inline-encryption.rst | 2 +
Documentation/filesystems/fscrypt.rst | 83 +++++++++++++++++++++++--------
fs/crypto/bio.c | 32 ++++++------
fs/crypto/fname.c | 3 +-
fs/crypto/fscrypt_private.h | 16 ++++--
fs/crypto/hkdf.c | 11 ++--
fs/crypto/keysetup.c | 62 +++++++++++++++++------
fs/ext4/super.c | 1 -
fs/f2fs/super.c | 1 -
fs/ubifs/crypto.c | 1 -
include/linux/fscrypt.h | 3 --
11 files changed, 150 insertions(+), 65 deletions(-)
next reply other threads:[~2021-10-31 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 23:15 Eric Biggers [this message]
2021-11-01 20:04 ` [GIT PULL] fscrypt updates for 5.16 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=YX8jdp73zUDwlB5E@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=linux-mtd@lists.infradead.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).