From: Tom Eccles <tom.eccles@codethink.co.uk>
To: dm-crypt@saout.de
Subject: [dm-crypt] Re: [DM-Verity] Corruption after activation during boot
Date: Wed, 24 Mar 2021 08:57:32 +0000 [thread overview]
Message-ID: <b93fde55-8d47-9188-f386-04b02949cc26@codethink.co.uk> (raw)
In-Reply-To: <CAA+CgzajXkSk0KUqbO-=wBp63+sYpHsyy8pyEtc1aU-tKMUQdQ@mail.gmail.com>
Hi Aditya,
On 3/20/21 11:22 AM, Aditya Prakash wrote:
> Hi,
> I am using the same device (/dev/sda2) for data and hash with --hash-offset
> set. The hash offset is set to 4096 added to the total space used in
> /dev/sda. When I verify the verity target without activating, it succeeds
> and gives valid (V) status. However, when I try to load it during boot, it
> gives an error with corruption at 0 and 1 block and is stuck in the boot
> loop.
>
> Is there something wrong I am doing with the hash-offset? Any help or
> guidance would be really appreciated.
This sounds similar to https://gitlab.com/cryptsetup/cryptsetup/-/issues/462
That issue should be fixed with Linux 5.12.
Tom
>
> Thanks,
> Aditya
>
>
> _______________________________________________
> dm-crypt mailing list -- dm-crypt@saout.de
> To unsubscribe send an email to dm-crypt-leave@saout.de
>
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2021-03-24 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 11:22 [dm-crypt] [DM-Verity] Corruption after activation during boot Aditya Prakash
2021-03-24 8:57 ` Tom Eccles [this message]
2021-03-24 9:45 ` [dm-crypt] " Milan Broz
2021-03-24 23:51 ` Aditya Prakash
2021-03-25 0:10 ` Milan Broz
2021-03-25 1:24 ` Aditya Prakash
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=b93fde55-8d47-9188-f386-04b02949cc26@codethink.co.uk \
--to=tom.eccles@codethink.co.uk \
--cc=dm-crypt@saout.de \
/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).