From: Eric Biggers <ebiggers@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
dm-devel@redhat.com, Jens Axboe <axboe@kernel.dk>,
Mike Snitzer <snitzer@redhat.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH v4 5/5] dm: set DM_TARGET_PASSES_CRYPTO feature for some targets
Date: Wed, 10 Feb 2021 12:24:58 -0800 [thread overview]
Message-ID: <YCRBGnGq/LY0uNxM@gmail.com> (raw)
In-Reply-To: <20210201051019.1174983-6-satyat@google.com>
On Mon, Feb 01, 2021 at 05:10:19AM +0000, Satya Tangirala wrote:
> dm-linear and dm-flakey obviously can pass through inline crypto support.
>
> Co-developed-by: Eric Biggers <ebiggers@google.com>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> Signed-off-by: Satya Tangirala <satyat@google.com>
> ---
> drivers/md/dm-flakey.c | 4 +++-
> drivers/md/dm-linear.c | 5 +++--
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/md/dm-flakey.c b/drivers/md/dm-flakey.c
> index a2cc9e45cbba..30c6bc151213 100644
> --- a/drivers/md/dm-flakey.c
> +++ b/drivers/md/dm-flakey.c
> @@ -482,8 +482,10 @@ static struct target_type flakey_target = {
> .name = "flakey",
> .version = {1, 5, 0},
> #ifdef CONFIG_BLK_DEV_ZONED
> - .features = DM_TARGET_ZONED_HM,
> + .features = DM_TARGET_ZONED_HM | DM_TARGET_PASSES_CRYPTO,
> .report_zones = flakey_report_zones,
> +#else
> + .features = DM_TARGET_PASSES_CRYPTO,
> #endif
> .module = THIS_MODULE,
> .ctr = flakey_ctr,
> diff --git a/drivers/md/dm-linear.c b/drivers/md/dm-linear.c
> index 00774b5d7668..fc9c4272c10d 100644
> --- a/drivers/md/dm-linear.c
> +++ b/drivers/md/dm-linear.c
> @@ -229,10 +229,11 @@ static struct target_type linear_target = {
> .version = {1, 4, 0},
> #ifdef CONFIG_BLK_DEV_ZONED
> .features = DM_TARGET_PASSES_INTEGRITY | DM_TARGET_NOWAIT |
> - DM_TARGET_ZONED_HM,
> + DM_TARGET_ZONED_HM | DM_TARGET_PASSES_CRYPTO,
> .report_zones = linear_report_zones,
> #else
> - .features = DM_TARGET_PASSES_INTEGRITY | DM_TARGET_NOWAIT,
> + .features = DM_TARGET_PASSES_INTEGRITY | DM_TARGET_NOWAIT |
> + DM_TARGET_PASSES_CRYPTO,
> #endif
> .module = THIS_MODULE,
> .ctr = linear_ctr,
> --
This latest version looks good to me. If it's needed despite my
Co-developed-by, feel free to add:
Reviewed-by: Eric Biggers <ebiggers@google.com>
BTW, the #ifdef for CONFIG_BLK_DEV_ZONED is error-prone (though it's a
pre-existing issue). I wonder if DM_TARGET_ZONED_HM should be defined to 0 when
!CONFIG_BLK_DEV_ZONED, which would avoid the need for the #ifdef on .features.
- Eric
next prev parent reply other threads:[~2021-02-10 20:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 5:10 [PATCH v4 0/5] add support for inline encryption to device mapper Satya Tangirala
2021-02-01 5:10 ` [PATCH v4 1/5] block: keyslot-manager: Introduce passthrough keyslot manager Satya Tangirala
2021-02-01 5:10 ` [PATCH v4 2/5] block: keyslot-manager: Introduce functions for device mapper support Satya Tangirala
2021-02-10 19:55 ` Eric Biggers
2021-02-01 5:10 ` [PATCH v4 3/5] dm: add support for passing through inline crypto support Satya Tangirala
2021-02-10 20:17 ` Eric Biggers
2021-02-11 22:58 ` Satya Tangirala
2021-02-01 5:10 ` [PATCH v4 4/5] dm: support key eviction from keyslot managers of underlying devices Satya Tangirala
2021-02-10 20:19 ` Eric Biggers
2021-02-01 5:10 ` [PATCH v4 5/5] dm: set DM_TARGET_PASSES_CRYPTO feature for some targets Satya Tangirala
2021-02-10 20:24 ` Eric Biggers [this message]
2021-02-10 19:33 ` [PATCH v4 0/5] add support for inline encryption to device mapper Mike Snitzer
2021-02-10 19:59 ` Jens Axboe
2021-02-11 23:01 ` Satya Tangirala
2021-02-11 23:04 ` Mike Snitzer
2021-02-12 0:47 ` Satya Tangirala
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=YCRBGnGq/LY0uNxM@gmail.com \
--to=ebiggers@kernel.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satyat@google.com \
--cc=snitzer@redhat.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