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>, Christoph Hellwig <hch@lst.de>
Subject: [GIT PULL] fscrypt updates for 6.1
Date: Sun, 2 Oct 2022 20:00:03 -0700 [thread overview]
Message-ID: <YzpQMx1FiZp/PsM3@quark> (raw)
The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:
Linux 6.0-rc2 (2022-08-21 17:32:54 -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 0e91fc1e0f5c70ce575451103ec66c2ec21f1a6e:
fscrypt: work on block_devices instead of request_queues (2022-09-21 20:33:06 -0700)
----------------------------------------------------------------
This release contains some implementation changes, but no new features:
- Rework the implementation of the fscrypt filesystem-level keyring to
not be as tightly coupled to the keyrings subsystem. This resolves
several issues.
- Eliminate most direct uses of struct request_queue from fs/crypto/,
since struct request_queue is considered to be a block layer
implementation detail.
- Stop using the PG_error flag to track decryption failures. This is a
prerequisite for freeing up PG_error for other uses.
----------------------------------------------------------------
Christoph Hellwig (1):
fscrypt: work on block_devices instead of request_queues
Eric Biggers (4):
fscrypt: remove fscrypt_set_test_dummy_encryption()
fscrypt: stop using PG_error to track error status
fscrypt: stop using keyrings subsystem for fscrypt_master_key
fscrypt: stop holding extra request_queue references
fs/crypto/bio.c | 16 +-
fs/crypto/fscrypt_private.h | 82 +++++---
fs/crypto/hooks.c | 10 +-
fs/crypto/inline_crypt.c | 147 +++++++------
fs/crypto/keyring.c | 495 ++++++++++++++++++++++++--------------------
fs/crypto/keysetup.c | 89 ++++----
fs/crypto/keysetup_v1.c | 4 +-
fs/crypto/policy.c | 21 +-
fs/ext4/readpage.c | 10 +-
fs/f2fs/data.c | 18 +-
fs/f2fs/super.c | 24 +--
fs/super.c | 2 +-
include/linux/fs.h | 2 +-
include/linux/fscrypt.h | 32 ++-
14 files changed, 495 insertions(+), 457 deletions(-)
next reply other threads:[~2022-10-03 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 3:00 Eric Biggers [this message]
2022-10-04 3:44 ` [GIT PULL] fscrypt updates for 6.1 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=YzpQMx1FiZp/PsM3@quark \
--to=ebiggers@kernel.org \
--cc=hch@lst.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).