All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Glenn Washburn <development@efficientek.com>
Cc: grub-devel@gnu.org, Daniel Kiper <dkiper@net-space.pl>,
	Pierre-Louis Bonicoli <pierre-louis.bonicoli@libregerbil.fr>,
	Josselin Poiret <dev@jpoiret.xyz>, Fabian Vogt <fvogt@suse.de>
Subject: Re: [PATCH 0/4] LUKS1/2 testing in fs-tester and LUKS2 support in grub-probe
Date: Fri, 13 Jan 2023 09:31:43 +0100	[thread overview]
Message-ID: <Y8EW78advUmG8en+@xps> (raw)
In-Reply-To: <20230112230510.1319896-1-development@efficientek.com>

[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]

On Thu, Jan 12, 2023 at 05:05:06PM -0600, Glenn Washburn wrote:
> This series adds the testing of LUKS 1 and 2 encrypted container to the
> user-space fs tester. While this does replicate some of the testing done
> by grub_cmd_cryptomount, and is less flexible, it is run natively (that is
> without need for virtualization). It also tests the added LUKS2 support in
> grub-probe, unlike grub_cmd_cryptomount which does not test any user-space
> grub components.
> 
> All of these patches have previously been sent to the list. Only patch 4 has
> been slightly modified to fix some issues. Since utility of any one is greatly
> enhanced, and in the case of patch 4 required, by the others, I think it makes
> sense to evaluate them together.

Yeah, makes sense to have them all in one place.

> Fabian has noted a memory leak with error handling when using LUKS2 with a
> null_cipher[1]. Since this isn't something that I expect to happen in the wild
> (why would you use an unencrypted LUKS container?) and even if it does occur
> grub-probe is exiting, so the leak would be very short lived, I don't think
> this is something that we need to worry about. It wouldn't be that hard to fix
> though, just annoying and add a little more complexity to the source.
> 
> The corresponding patches can be found in the order of this series here:
>  1: [PATCH v3] disk/cryptodisk: When cheatmounting, use the sector info of the cheat device
>     https://lists.gnu.org/archive/html/grub-devel/2022-06/msg00106.html
>  2: [PATCH v6 1/2] devmapper/getroot: Have devmapper recognize LUKS2
>     https://lists.gnu.org/archive/html/grub-devel/2022-07/msg00036.html
>  3: [PATCH v6 2/2] devmapper/getroot: Set up cheated LUKS2 cryptodisk mount from DM parameters
>     https://lists.gnu.org/archive/html/grub-devel/2022-07/msg00038.html
>  4: [PATCH v4] grub-fs-tester: Add luks1 and luks2 support
>     https://lists.gnu.org/archive/html/grub-devel/2022-06/msg00127.html

For all patches:

    Reviewed-by: Patrick Steinhardt <ps@pks.im>

Thanks a bunch!

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-01-13  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 23:05 [PATCH 0/4] LUKS1/2 testing in fs-tester and LUKS2 support in grub-probe Glenn Washburn
2023-01-12 23:05 ` [PATCH 1/4] disk/cryptodisk: When cheatmounting, use the sector info of the cheat device Glenn Washburn
2023-01-12 23:05 ` [PATCH 2/4] devmapper/getroot: Have devmapper recognize LUKS2 Glenn Washburn
2023-01-12 23:05 ` [PATCH 3/4] devmapper/getroot: Set up cheated LUKS2 cryptodisk mount from DM parameters Glenn Washburn
2023-01-13  8:29   ` Patrick Steinhardt
2023-01-13 22:14   ` Vladimir 'phcoder' Serbinenko
2023-01-12 23:05 ` [PATCH 4/4] grub-fs-tester: Add luks1 and luks2 support Glenn Washburn
2023-01-13  8:31 ` Patrick Steinhardt [this message]
2023-01-16 20:58   ` [PATCH 0/4] LUKS1/2 testing in fs-tester and LUKS2 support in grub-probe Glenn Washburn
2023-01-25 19:17   ` Daniel Kiper

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=Y8EW78advUmG8en+@xps \
    --to=ps@pks.im \
    --cc=dev@jpoiret.xyz \
    --cc=development@efficientek.com \
    --cc=dkiper@net-space.pl \
    --cc=fvogt@suse.de \
    --cc=grub-devel@gnu.org \
    --cc=pierre-louis.bonicoli@libregerbil.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.