From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Hyman Huang <yong.huang@smartx.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Hanna Reitz <hreitz@redhat.com>, Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH RESEND v3 05/10] crypto: Mark the payload_offset_sector invalid for detached LUKS header
Date: Thu, 4 Jan 2024 14:48:34 +0000 [thread overview]
Message-ID: <ZZbFQod-d0Zt95M6@redhat.com> (raw)
In-Reply-To: <02d08ca67a4ec88cee61446d6b330c2945b5588f.1703482349.git.yong.huang@smartx.com>
On Mon, Dec 25, 2023 at 01:45:07PM +0800, Hyman Huang wrote:
> Set the payload_offset_sector to a value that is nearly never reached
> in order to mark it as invalid and indicate that 0 should be the offset
> of the read/write operation on the 'file' protocol blockdev node.
>
> Signed-off-by: Hyman Huang <yong.huang@smartx.com>
> ---
> crypto/block-luks.c | 41 +++++++++++++++++++++++++++++++----------
> 1 file changed, 31 insertions(+), 10 deletions(-)
>
> diff --git a/crypto/block-luks.c b/crypto/block-luks.c
> index fb01ec38bb..48443ffcae 100644
> --- a/crypto/block-luks.c
> +++ b/crypto/block-luks.c
> @@ -34,6 +34,8 @@
>
> #include "qemu/bitmap.h"
>
> +#define INVALID_SECTOR_OFFSET UINT32_MAX
> +
> /*
> * Reference for the LUKS format implemented here is
> *
> @@ -136,6 +138,13 @@ struct QCryptoBlockLUKS {
> };
>
>
> +static inline uint32_t
> +qcrypto_block_luks_payload_offset(uint32_t sector)
> +{
> + return sector == INVALID_SECTOR_OFFSET ? 0 :
> + sector * QCRYPTO_BLOCK_LUKS_SECTOR_SIZE;
> +}
> +
> static int qcrypto_block_luks_cipher_name_lookup(const char *name,
> QCryptoCipherMode mode,
> uint32_t key_bytes,
> @@ -1255,8 +1264,8 @@ qcrypto_block_luks_open(QCryptoBlock *block,
> }
>
> block->sector_size = QCRYPTO_BLOCK_LUKS_SECTOR_SIZE;
> - block->payload_offset = luks->header.payload_offset_sector *
> - block->sector_size;
> + block->payload_offset =
> + qcrypto_block_luks_payload_offset(luks->header.payload_offset_sector);
>
> return 0;
>
> @@ -1529,16 +1538,28 @@ qcrypto_block_luks_create(QCryptoBlock *block,
> slot->stripes = QCRYPTO_BLOCK_LUKS_STRIPES;
> }
>
> - /* The total size of the LUKS headers is the partition header + key
> - * slot headers, rounded up to the nearest sector, combined with
> - * the size of each master key material region, also rounded up
> - * to the nearest sector */
> - luks->header.payload_offset_sector = header_sectors +
> - QCRYPTO_BLOCK_LUKS_NUM_KEY_SLOTS * split_key_sectors;
> + if (block->detached_header) {
> + /*
> + * Set the payload_offset_sector to a value that is nearly never
> + * reached in order to mark it as invalid and indicate that 0 should
> + * be the offset of the read/write operation on the 'file' protocol
> + * blockdev node. Here the UINT32_MAX is choosed
> + */
> + luks->header.payload_offset_sector = INVALID_SECTOR_OFFSET;
We should be setting payload offset to 0 when using a detached header
to match behaviour of 'cryptsetup' tools.
> + } else {
> + /*
> + * The total size of the LUKS headers is the partition header + key
> + * slot headers, rounded up to the nearest sector, combined with
> + * the size of each master key material region, also rounded up
> + * to the nearest sector
> + */
> + luks->header.payload_offset_sector = header_sectors +
> + QCRYPTO_BLOCK_LUKS_NUM_KEY_SLOTS * split_key_sectors;
> + }
>
> block->sector_size = QCRYPTO_BLOCK_LUKS_SECTOR_SIZE;
> - block->payload_offset = luks->header.payload_offset_sector *
> - block->sector_size;
> + block->payload_offset =
> + qcrypto_block_luks_payload_offset(luks->header.payload_offset_sector);
>
> /* Reserve header space to match payload offset */
> initfunc(block, block->payload_offset, opaque, &local_err);
> --
> 2.39.1
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-01-04 14:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 5:45 [PATCH RESEND v3 00/10] Support generic Luks encryption Hyman Huang
2023-12-25 5:45 ` [PATCH RESEND v3 01/10] crypto: Introduce option and structure for detached LUKS header Hyman Huang
2024-01-11 14:35 ` Markus Armbruster
2024-01-11 14:58 ` Daniel P. Berrangé
2024-01-11 16:02 ` Yong Huang
2023-12-25 5:45 ` [PATCH RESEND v3 02/10] crypto: Support generic LUKS encryption Hyman Huang
2024-01-04 14:39 ` Daniel P. Berrangé
2024-01-07 11:56 ` Yong Huang
2023-12-25 5:45 ` [PATCH RESEND v3 03/10] qapi: Make parameter 'file' optional for BlockdevCreateOptionsLUKS Hyman Huang
2024-01-04 14:40 ` Daniel P. Berrangé
2023-12-25 5:45 ` [PATCH RESEND v3 04/10] crypto: Introduce creation option and structure for detached LUKS header Hyman Huang
2024-01-04 14:51 ` Daniel P. Berrangé
2024-01-07 11:58 ` Yong Huang
2023-12-25 5:45 ` [PATCH RESEND v3 05/10] crypto: Mark the payload_offset_sector invalid " Hyman Huang
2024-01-04 14:48 ` Daniel P. Berrangé [this message]
2023-12-25 5:45 ` [PATCH RESEND v3 06/10] block: Support detached LUKS header creation using blockdev-create Hyman Huang
2024-01-04 14:47 ` Daniel P. Berrangé
2024-01-11 14:05 ` Markus Armbruster
2024-01-11 15:52 ` Yong Huang
2023-12-25 5:45 ` [PATCH RESEND v3 07/10] block: Support detached LUKS header creation using qemu-img Hyman Huang
2023-12-25 5:45 ` [PATCH RESEND v3 08/10] crypto: Introduce 'detached-header' field in QCryptoBlockInfoLUKS Hyman Huang
2024-01-04 14:59 ` Daniel P. Berrangé
2023-12-25 5:45 ` [PATCH RESEND v3 09/10] tests: Add detached LUKS header case Hyman Huang
2023-12-25 5:45 ` [PATCH RESEND v3 10/10] MAINTAINERS: Add section "Detached LUKS header" Hyman Huang
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=ZZbFQod-d0Zt95M6@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yong.huang@smartx.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).