From: Eric Biggers <ebiggers@kernel.org>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: linux-fscrypt@vger.kernel.org, Nathan Huckleberry <nhuck@google.com>
Subject: [PATCH 0/3] Fix blk-crypto keyslot race condition
Date: Thu, 2 Mar 2023 23:19:56 -0800 [thread overview]
Message-ID: <20230303071959.144604-1-ebiggers@kernel.org> (raw)
This series fixes a race condition in blk-crypto keyslot management and
makes some related cleanups. It replaces
"[PATCH] blk-crypto: make blk_crypto_evict_key() always try to evict"
(https://lore.kernel.org/r/20230226203816.207449-1-ebiggers@kernel.org),
which was a simpler fix but didn't fix the keyslot reference counting to
work as expected.
Eric Biggers (3):
blk-mq: release crypto keyslot before reporting I/O complete
blk-crypto: make blk_crypto_evict_key() more robust
blk-crypto: remove blk_crypto_insert_cloned_request()
Documentation/block/inline-encryption.rst | 3 +-
block/blk-crypto-internal.h | 28 +++++--------
block/blk-crypto-profile.c | 50 +++++++++--------------
block/blk-crypto.c | 47 +++++++++++----------
block/blk-mq.c | 17 +++++++-
5 files changed, 71 insertions(+), 74 deletions(-)
base-commit: 2eb29d59ddf02e39774abfb60b2030b0b7e27c1f
--
2.39.2
next reply other threads:[~2023-03-03 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 7:19 Eric Biggers [this message]
2023-03-03 7:19 ` [PATCH 1/3] blk-mq: release crypto keyslot before reporting I/O complete Eric Biggers
2023-03-03 19:29 ` Nathan Huckleberry
2023-03-08 18:21 ` Eric Biggers
2023-03-03 7:19 ` [PATCH 2/3] blk-crypto: make blk_crypto_evict_key() more robust Eric Biggers
2023-03-03 19:45 ` Nathan Huckleberry
2023-03-03 19:50 ` Eric Biggers
2023-03-03 20:30 ` Nathan Huckleberry
2023-03-03 7:19 ` [PATCH 3/3] blk-crypto: remove blk_crypto_insert_cloned_request() 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=20230303071959.144604-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=nhuck@google.com \
/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).