From: Eric Biggers <ebiggers@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Josef Bacik <josef@toxicpanda.com>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH 0/3] Move fscrypt keyring destruction to after ->put_super
Date: Tue, 12 Dec 2023 20:00:15 -0800 [thread overview]
Message-ID: <20231213040018.73803-1-ebiggers@kernel.org> (raw)
This series moves the fscrypt keyring destruction to after ->put_super,
as this will be needed by the btrfs fscrypt support. To make this
possible, it also changes btrfs and f2fs to release their block devices
after generic_shutdown_super() rather than before.
This supersedes "[PATCH] fscrypt: move the call to
fscrypt_destroy_keyring() into ->put_super()"
(https://lore.kernel.org/linux-fscrypt/20231206001325.13676-1-ebiggers@kernel.org/T/#u)
This applies to v6.7-rc5.
Christoph Hellwig (1):
btrfs: call btrfs_close_devices from ->kill_sb
Eric Biggers (1):
f2fs: move release of block devices to after kill_block_super()
Josef Bacik (1):
fs: move fscrypt keyring destruction to after ->put_super
fs/btrfs/disk-io.c | 4 ++--
fs/btrfs/super.c | 7 ++-----
fs/f2fs/super.c | 12 +++++++-----
fs/super.c | 12 ++++++------
4 files changed, 17 insertions(+), 18 deletions(-)
base-commit: a39b6ac3781d46ba18193c9dbb2110f31e9bffe9
--
2.43.0
next reply other threads:[~2023-12-13 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 4:00 Eric Biggers [this message]
2023-12-13 4:00 ` [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb Eric Biggers
2023-12-13 8:41 ` Christoph Hellwig
2023-12-15 14:26 ` Josef Bacik
2023-12-15 21:45 ` [f2fs-dev] " Josef Bacik
2023-12-16 4:12 ` Christoph Hellwig
2023-12-16 14:52 ` Josef Bacik
2023-12-13 4:00 ` [PATCH 2/3] f2fs: move release of block devices to after kill_block_super() Eric Biggers
2023-12-27 4:47 ` Eric Biggers
2023-12-27 7:10 ` [f2fs-dev] " Chao Yu
2023-12-13 4:00 ` [PATCH 3/3] fs: move fscrypt keyring destruction to after ->put_super Eric Biggers
2023-12-13 16:15 ` Christoph Hellwig
2023-12-13 20:54 ` Neal Gompa
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=20231213040018.73803-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@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 read-only IMAP folder(s) and NNTP newsgroup(s).