From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Qianfeng Rong <rongqianfeng@vivo.com>
Subject: [GIT PULL] fscrypt updates for 6.18
Date: Sat, 27 Sep 2025 12:48:16 -0700 [thread overview]
Message-ID: <20250927194816.GA8682@quark> (raw)
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus
for you to fetch changes up to 19591f7e781fd1e68228f5b3bee60be6425af886:
fscrypt: use HMAC-SHA512 library for HKDF (2025-09-05 21:01:51 -0700)
----------------------------------------------------------------
Make fs/crypto/ use the HMAC-SHA512 library functions instead of
crypto_shash. This is simpler, faster, and more reliable.
----------------------------------------------------------------
Eric Biggers (1):
fscrypt: use HMAC-SHA512 library for HKDF
Qianfeng Rong (1):
fscrypt: Remove redundant __GFP_NOWARN
fs/crypto/Kconfig | 5 +-
fs/crypto/bio.c | 2 +-
fs/crypto/fname.c | 1 -
fs/crypto/fscrypt_private.h | 26 ++++-------
fs/crypto/hkdf.c | 109 ++++++++++++++++----------------------------
fs/crypto/hooks.c | 2 +-
fs/crypto/keyring.c | 30 ++++--------
fs/crypto/keysetup.c | 65 ++++++++------------------
fs/crypto/policy.c | 4 +-
9 files changed, 83 insertions(+), 161 deletions(-)
next reply other threads:[~2025-09-27 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 19:48 Eric Biggers [this message]
2025-09-29 23:22 ` [GIT PULL] fscrypt updates for 6.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=20250927194816.GA8682@quark \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rongqianfeng@vivo.com \
--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