From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Mike Snitzer <snitzer@kernel.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
linux-fscrypt@vger.kernel.org
Subject: pass a struct block_device to the blk-crypto interfaces v3
Date: Mon, 14 Nov 2022 05:29:41 +0100 [thread overview]
Message-ID: <20221114042944.1009870-1-hch@lst.de> (raw)
Hi all,
this series switches the blk-crypto interfaces to take block_device
arguments instead of request_queues, and with that finishes off the
project to hide struct request_queue from file systems.
Changes since v2:
- update a few comments
- fix a whitespace error
- remove now unused forward declarations
- fix spelling errors an not precise enough wording in commit messages
- move a few more declarations around inside or between headers
Changes since v1:
- keep using request_queue in the Documentation for driver interfaces
- rename to blk_crypto_cfg_supported to
blk_crypto_config_supported_natively and move it to blk-crypto.[ch]
- mark __blk_crypto_cfg_supported private
Diffstat:
Documentation/block/inline-encryption.rst | 12 ++++-----
block/blk-crypto-internal.h | 12 +++++++++
block/blk-crypto.c | 37 +++++++++++++++++-------------
drivers/md/dm-table.c | 2 -
fs/crypto/inline_crypt.c | 14 ++++-------
include/linux/blk-crypto-profile.h | 12 ---------
include/linux/blk-crypto.h | 13 ++++------
7 files changed, 52 insertions(+), 50 deletions(-)
next reply other threads:[~2022-11-14 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 4:29 Christoph Hellwig [this message]
2022-11-14 4:29 ` [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces Christoph Hellwig
2022-11-16 3:10 ` Eric Biggers
2022-11-14 4:29 ` [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper Christoph Hellwig
2022-11-16 3:12 ` Eric Biggers
2022-11-14 4:29 ` [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h Christoph Hellwig
2022-11-15 9:06 ` [dm-devel] " Christoph Hellwig
2022-11-16 3:18 ` Eric Biggers
2022-11-21 18:39 ` pass a struct block_device to the blk-crypto interfaces v3 Jens Axboe
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=20221114042944.1009870-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=snitzer@kernel.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).