From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH 0/2] fscrypt: rework filesystem-level keyring
Date: Fri, 19 Aug 2022 00:15:30 -0700 [thread overview]
Message-ID: <20220819071532.221026-1-ebiggers@kernel.org> (raw)
This series reworks the filesystem-level keyring to not use the keyrings
subsystem as part of its internal implementation (except for ->mk_users,
which remains unchanged for now). This fixes several issues, described
in the first patch. This is also a prerequisite for removing the direct
use of struct request_queue from filesystem code, as discussed at
https://lore.kernel.org/linux-fscrypt/20220721125929.1866403-1-hch@lst.de/T/#u
Eric Biggers (2):
fscrypt: stop using keyrings subsystem for fscrypt_master_key
fscrypt: stop holding extra request_queue references
fs/crypto/fscrypt_private.h | 74 ++++--
fs/crypto/hooks.c | 10 +-
fs/crypto/inline_crypt.c | 83 +++----
fs/crypto/keyring.c | 476 +++++++++++++++++++-----------------
fs/crypto/keysetup.c | 89 +++----
fs/crypto/keysetup_v1.c | 4 +-
fs/crypto/policy.c | 8 +-
fs/super.c | 2 +-
include/linux/fs.h | 2 +-
include/linux/fscrypt.h | 4 +-
10 files changed, 387 insertions(+), 365 deletions(-)
base-commit: 568035b01cfb107af8d2e4bd2fb9aea22cf5b868
--
2.37.1
next reply other threads:[~2022-08-19 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 7:15 Eric Biggers [this message]
2022-08-19 7:15 ` [PATCH 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key Eric Biggers
2022-08-19 7:15 ` [PATCH 2/2] fscrypt: stop holding extra request_queue references Eric Biggers
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=20220819071532.221026-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.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 \
/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).