linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-ext4@vger.kernel.org,
	Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
	Kuohong Wang <kuohong.wang@mediatek.com>,
	Kim Boojin <boojin.kim@samsung.com>
Subject: Re: [PATCH v11 04/12] block: Make blk-integrity preclude hardware inline encryption
Date: Thu, 30 Apr 2020 00:11:19 -0700	[thread overview]
Message-ID: <20200430071119.GC16238@sol.localdomain> (raw)
In-Reply-To: <20200429072121.50094-5-satyat@google.com>

On Wed, Apr 29, 2020 at 07:21:13AM +0000, Satya Tangirala wrote:
> Whenever a device supports blk-integrity, the kernel will now always
> pretend that the device doesn't support inline encryption (essentially
> by setting the keyslot manager in the request queue to NULL).

"the kernel will now always" => "make the kernel", so that it's clear that this
patch is doing this.  I.e. it's not describing the state prior to the patch.

> diff --git a/block/blk-integrity.c b/block/blk-integrity.c
> index ff1070edbb400..b45711fc37df4 100644
> --- a/block/blk-integrity.c
> +++ b/block/blk-integrity.c
> @@ -409,6 +409,13 @@ void blk_integrity_register(struct gendisk *disk, struct blk_integrity *template
>  	bi->tag_size = template->tag_size;
>  
>  	disk->queue->backing_dev_info->capabilities |= BDI_CAP_STABLE_WRITES;
> +
> +#ifdef CONFIG_BLK_INLINE_ENCRYPTION
> +	if (disk->queue->ksm) {
> +		pr_warn("blk-integrity: Integrity and hardware inline encryption are not supported together. Unregistering keyslot manager from request queue, to disable hardware inline encryption.\n");
> +		blk_ksm_unregister(disk->queue);
> +	}
> +#endif
>  }

Make this shorter by removing the mention of the keyslot manager?:

	pr_warn("blk-integrity: Integrity and hardware inline encryption are not supported together. Disabling hardware inline encryption.\n");


> diff --git a/block/keyslot-manager.c b/block/keyslot-manager.c
> index b584723b392ad..834f45fdd33e2 100644
> --- a/block/keyslot-manager.c
> +++ b/block/keyslot-manager.c
> @@ -25,6 +25,9 @@
>   * Upper layers will call blk_ksm_get_slot_for_key() to program a
>   * key into some slot in the inline encryption hardware.
>   */
> +
> +#define pr_fmt(fmt) "blk_crypto: " fmt

"blk-crypto", not "blk_crypto".

> +bool blk_ksm_register(struct blk_keyslot_manager *ksm, struct request_queue *q)
> +{
> +	if (blk_integrity_queue_supports_integrity(q)) {
> +		pr_warn("Integrity and hardware inline encryption are not supported together. Hardware inline encryption is being disabled.\n");

"Disabling hardware inline encryption" to match my suggestion for the other one?

- Eric

  reply	other threads:[~2020-04-30  7:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  7:21 [PATCH v11 00/12] Inline Encryption Support Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 01/12] Documentation: Document the blk-crypto framework Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 02/12] block: Keyslot Manager for Inline Encryption Satya Tangirala
2020-04-30  6:46   ` Eric Biggers
2020-04-29  7:21 ` [PATCH v11 03/12] block: Inline encryption support for blk-mq Satya Tangirala
2020-04-30  7:01   ` Eric Biggers
2020-04-29  7:21 ` [PATCH v11 04/12] block: Make blk-integrity preclude hardware inline encryption Satya Tangirala
2020-04-30  7:11   ` Eric Biggers [this message]
2020-04-29  7:21 ` [PATCH v11 05/12] block: blk-crypto-fallback for Inline Encryption Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 06/12] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 07/12] scsi: ufs: UFS crypto API Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 08/12] scsi: ufs: Add inline encryption support to UFS Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 09/12] fs: introduce SB_INLINECRYPT Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 10/12] fscrypt: add inline encryption support Satya Tangirala
2020-04-30  7:24   ` Eric Biggers
2020-04-29  7:21 ` [PATCH v11 11/12] f2fs: " Satya Tangirala
2020-04-29  7:21 ` [PATCH v11 12/12] ext4: " Satya Tangirala
2020-04-29 15:41 ` [PATCH v11 00/12] Inline Encryption Support 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=20200430071119.GC16238@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=bmuthuku@qti.qualcomm.com \
    --cc=boojin.kim@samsung.com \
    --cc=kuohong.wang@mediatek.com \
    --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 \
    --cc=linux-scsi@vger.kernel.org \
    --cc=satyat@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).