From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
ceph-devel@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 6.4
Date: Mon, 24 Apr 2023 23:24:51 -0700 [thread overview]
Message-ID: <20230425062451.GA77408@sol.localdomain> (raw)
The following changes since commit 197b6b60ae7bc51dd0814953c562833143b292aa:
Linux 6.3-rc4 (2023-03-26 14:40:20 -0700)
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 83e57e47906ce0e99bd61c70fae514e69960d274:
fscrypt: optimize fscrypt_initialize() (2023-04-06 11:16:39 -0700)
----------------------------------------------------------------
A few cleanups for fs/crypto/, and another patch to prepare for the
upcoming CephFS encryption support.
----------------------------------------------------------------
Eric Biggers (3):
fs/buffer.c: use b_folio for fscrypt work
fscrypt: use WARN_ON_ONCE instead of WARN_ON
fscrypt: optimize fscrypt_initialize()
Luís Henriques (1):
fscrypt: new helper function - fscrypt_prepare_lookup_partial()
fs/buffer.c | 4 ++--
fs/crypto/bio.c | 6 +++---
fs/crypto/crypto.c | 19 ++++++++++++-------
fs/crypto/fname.c | 4 ++--
fs/crypto/fscrypt_private.h | 6 +++---
fs/crypto/hkdf.c | 4 ++--
fs/crypto/hooks.c | 32 +++++++++++++++++++++++++++++++-
fs/crypto/keyring.c | 14 +++++++-------
fs/crypto/keysetup.c | 14 +++++++-------
fs/crypto/policy.c | 4 ++--
include/linux/fscrypt.h | 7 +++++++
11 files changed, 78 insertions(+), 36 deletions(-)
next reply other threads:[~2023-04-25 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 6:24 Eric Biggers [this message]
2023-04-26 17:06 ` [GIT PULL] fscrypt updates for 6.4 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=20230425062451.GA77408@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ceph-devel@vger.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=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).