From: Mikulas Patocka <mpatocka@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Md Sadre Alam <quic_mdalam@quicinc.com>,
Israel Rukshin <israelr@nvidia.com>,
Milan Broz <gmazyland@gmail.com>,
Adrian Vovk <adrianvovk@gmail.com>
Subject: Re: [RFC PATCH 2/4] block: add the bi_skip_dm_default_key flag
Date: Mon, 21 Oct 2024 13:11:36 +0200 (CEST) [thread overview]
Message-ID: <2caf648d-73cf-9436-2af4-ad530a966592@redhat.com> (raw)
In-Reply-To: <20241018184339.66601-3-ebiggers@kernel.org>
Hi
What about using the REQ_META flag (it is set on metadata bios and cleared
on data bios), instead of adding a new flag with the same meaning?
Mikulas
On Fri, 18 Oct 2024, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Add a flag bi_skip_dm_default_key to struct bio. This flag indicates
> that dm-default-key should not en/decrypt the bio, due to it targeting
> the contents of an encrypted file.
>
> When a bio is cloned, copy the bi_skip_dm_default_key flag.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> block/bio.c | 3 +++
> block/blk-crypto-fallback.c | 2 ++
> include/linux/blk-crypto.h | 36 ++++++++++++++++++++++++++++++++++++
> include/linux/blk_types.h | 3 +++
> 4 files changed, 44 insertions(+)
>
> diff --git a/block/bio.c b/block/bio.c
> index ac4d77c889322..5ff0b66e47a42 100644
> --- a/block/bio.c
> +++ b/block/bio.c
> @@ -267,10 +267,13 @@ void bio_init(struct bio *bio, struct block_device *bdev, struct bio_vec *table,
> bio->bi_iocost_cost = 0;
> #endif
> #endif
> #ifdef CONFIG_BLK_INLINE_ENCRYPTION
> bio->bi_crypt_context = NULL;
> +#if IS_ENABLED(CONFIG_DM_DEFAULT_KEY)
> + bio->bi_skip_dm_default_key = false;
> +#endif
> #endif
> #ifdef CONFIG_BLK_DEV_INTEGRITY
> bio->bi_integrity = NULL;
> #endif
> bio->bi_vcnt = 0;
> diff --git a/block/blk-crypto-fallback.c b/block/blk-crypto-fallback.c
> index b1e7415f8439c..dd5f1edcc44b3 100644
> --- a/block/blk-crypto-fallback.c
> +++ b/block/blk-crypto-fallback.c
> @@ -179,10 +179,12 @@ static struct bio *blk_crypto_fallback_clone_bio(struct bio *bio_src)
> bio_for_each_segment(bv, bio_src, iter)
> bio->bi_io_vec[bio->bi_vcnt++] = bv;
>
> bio_clone_blkg_association(bio, bio_src);
>
> + bio_clone_skip_dm_default_key(bio, bio_src);
> +
> return bio;
> }
>
> static bool
> blk_crypto_fallback_alloc_cipher_req(struct blk_crypto_keyslot *slot,
> diff --git a/include/linux/blk-crypto.h b/include/linux/blk-crypto.h
> index 5e5822c18ee41..f1f3d546c53e5 100644
> --- a/include/linux/blk-crypto.h
> +++ b/include/linux/blk-crypto.h
> @@ -110,10 +110,13 @@ static inline bool bio_has_crypt_ctx(struct bio *bio)
> return false;
> }
>
> #endif /* CONFIG_BLK_INLINE_ENCRYPTION */
>
> +static inline void bio_clone_skip_dm_default_key(struct bio *dst,
> + const struct bio *src);
> +
> int __bio_crypt_clone(struct bio *dst, struct bio *src, gfp_t gfp_mask);
> /**
> * bio_crypt_clone - clone bio encryption context
> * @dst: destination bio
> * @src: source bio
> @@ -125,11 +128,44 @@ int __bio_crypt_clone(struct bio *dst, struct bio *src, gfp_t gfp_mask);
> * @gfp_mask doesn't include %__GFP_DIRECT_RECLAIM.
> */
> static inline int bio_crypt_clone(struct bio *dst, struct bio *src,
> gfp_t gfp_mask)
> {
> + bio_clone_skip_dm_default_key(dst, src);
> if (bio_has_crypt_ctx(src))
> return __bio_crypt_clone(dst, src, gfp_mask);
> return 0;
> }
>
> +#if IS_ENABLED(CONFIG_DM_DEFAULT_KEY)
> +static inline void bio_set_skip_dm_default_key(struct bio *bio)
> +{
> + bio->bi_skip_dm_default_key = true;
> +}
> +
> +static inline bool bio_should_skip_dm_default_key(const struct bio *bio)
> +{
> + return bio->bi_skip_dm_default_key;
> +}
> +
> +static inline void bio_clone_skip_dm_default_key(struct bio *dst,
> + const struct bio *src)
> +{
> + dst->bi_skip_dm_default_key = src->bi_skip_dm_default_key;
> +}
> +#else /* CONFIG_DM_DEFAULT_KEY */
> +static inline void bio_set_skip_dm_default_key(struct bio *bio)
> +{
> +}
> +
> +static inline bool bio_should_skip_dm_default_key(const struct bio *bio)
> +{
> + return false;
> +}
> +
> +static inline void bio_clone_skip_dm_default_key(struct bio *dst,
> + const struct bio *src)
> +{
> +}
> +#endif /* !CONFIG_DM_DEFAULT_KEY */
> +
> #endif /* __LINUX_BLK_CRYPTO_H */
> diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
> index dce7615c35e7e..2ee6a7e570796 100644
> --- a/include/linux/blk_types.h
> +++ b/include/linux/blk_types.h
> @@ -247,10 +247,13 @@ struct bio {
> #endif
> #endif
>
> #ifdef CONFIG_BLK_INLINE_ENCRYPTION
> struct bio_crypt_ctx *bi_crypt_context;
> +#if IS_ENABLED(CONFIG_DM_DEFAULT_KEY)
> + bool bi_skip_dm_default_key;
> +#endif
> #endif
>
> #if defined(CONFIG_BLK_DEV_INTEGRITY)
> struct bio_integrity_payload *bi_integrity; /* data integrity */
> #endif
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-10-21 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 18:43 [RFC PATCH 0/4] dm-default-key: target for filesystem metadata encryption Eric Biggers
2024-10-18 18:43 ` [RFC PATCH 1/4] block: export blk-crypto symbols required by dm-default-key Eric Biggers
2024-10-18 18:43 ` [RFC PATCH 2/4] block: add the bi_skip_dm_default_key flag Eric Biggers
2024-10-21 11:11 ` Mikulas Patocka [this message]
2024-10-21 19:02 ` Eric Biggers
2024-10-18 18:43 ` [RFC PATCH 3/4] dm-default-key: add target for filesystem metadata encryption Eric Biggers
2024-10-18 18:43 ` [RFC PATCH 4/4] ext4,f2fs: support metadata encryption via dm-default-key Eric Biggers
2024-10-21 11:52 ` [RFC PATCH 0/4] dm-default-key: target for filesystem metadata encryption Mikulas Patocka
2024-10-21 19:10 ` 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=2caf648d-73cf-9436-2af4-ad530a966592@redhat.com \
--to=mpatocka@redhat.com \
--cc=adrianvovk@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=israelr@nvidia.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-kernel@vger.kernel.org \
--cc=quic_mdalam@quicinc.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