Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-block@vger.kernel.org
Subject: [PATCH 6.1 0/7] blk-crypto fixes for 6.1
Date: Wed,  3 May 2023 20:54:10 -0700	[thread overview]
Message-ID: <20230504035417.61435-1-ebiggers@kernel.org> (raw)

This series backports a couple blk-crypto fixes and their prerequisites
to 6.1-stable.  All are clean cherry-picks, but I'm sending this out
explicitly since the prerequisites might not have been obvious.

Bart Van Assche (1):
  blk-crypto: Add a missing include directive

Christoph Hellwig (3):
  blk-crypto: don't use struct request_queue for public interfaces
  blk-crypto: add a blk_crypto_config_supported_natively helper
  blk-crypto: move internal only declarations to blk-crypto-internal.h

Eric Biggers (3):
  blk-mq: release crypto keyslot before reporting I/O complete
  blk-crypto: make blk_crypto_evict_key() return void
  blk-crypto: make blk_crypto_evict_key() more robust

 Documentation/block/inline-encryption.rst | 12 +--
 block/blk-crypto-internal.h               | 37 ++++++++-
 block/blk-crypto-profile.c                | 47 ++++++-----
 block/blk-crypto.c                        | 95 +++++++++++++----------
 block/blk-merge.c                         |  2 +
 block/blk-mq.c                            | 15 +++-
 drivers/md/dm-table.c                     | 19 ++---
 fs/crypto/inline_crypt.c                  | 14 ++--
 include/linux/blk-crypto-profile.h        | 12 ---
 include/linux/blk-crypto.h                | 15 ++--
 10 files changed, 150 insertions(+), 118 deletions(-)


base-commit: ca48fc16c49388400eddd6c6614593ebf7c7726a
-- 
2.40.1


             reply	other threads:[~2023-05-04  3:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  3:54 Eric Biggers [this message]
2023-05-04  3:54 ` [PATCH 6.1 1/7] blk-crypto: don't use struct request_queue for public interfaces Eric Biggers
2023-05-04  3:54 ` [PATCH 6.1 2/7] blk-crypto: add a blk_crypto_config_supported_natively helper Eric Biggers
2023-05-04  3:54 ` [PATCH 6.1 3/7] blk-crypto: move internal only declarations to blk-crypto-internal.h Eric Biggers
2023-05-04  3:54 ` [PATCH 6.1 4/7] blk-crypto: Add a missing include directive Eric Biggers
2023-05-04  3:54 ` [PATCH 6.1 5/7] blk-mq: release crypto keyslot before reporting I/O complete Eric Biggers
2023-05-04  3:54 ` [PATCH 6.1 6/7] blk-crypto: make blk_crypto_evict_key() return void Eric Biggers
2023-05-04  3:54 ` [PATCH 6.1 7/7] blk-crypto: make blk_crypto_evict_key() more robust Eric Biggers
2023-05-06  2:06 ` [PATCH 6.1 0/7] blk-crypto fixes for 6.1 Greg KH

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=20230504035417.61435-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=stable@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