From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.4 required=3.0 tests=BAYES_40,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB15CC433C1 for ; Sat, 20 Mar 2021 11:26:02 +0000 (UTC) Received: from mail.server123.net (mail.server123.net [78.46.64.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1E90261931 for ; Sat, 20 Mar 2021 11:26:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1E90261931 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=cs.stonybrook.edu Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dm-crypt-bounces@saout.de X-Virus-Scanned: amavisd-new at saout.de Authentication-Results: mail.server123.net (amavisd-new); dkim=pass (1024-bit key) header.d=stonybrook.edu Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::f2a; helo=mail-qv1-xf2a.google.com; envelope-from=adiprakash@cs.stonybrook.edu; receiver= Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sat, 20 Mar 2021 12:22:53 +0100 (CET) Received: by mail-qv1-xf2a.google.com with SMTP id g8so6367144qvx.1 for ; Sat, 20 Mar 2021 04:22:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stonybrook.edu; s=sbu-gmail; h=mime-version:from:date:message-id:subject:to; bh=sGtjiAz9Y2BLsXTL1GINxItJ9npoYiGCTATZNW71kbM=; b=YuKItVuE69upuUkRQqwGhT3lfXzQ44XSznv/HQ7FT7jRYrMvbGky4CGk0b4dou33J+ 3JWbSJWZ5sFb0G3sOKAqEfE0kBly7FlyD6geBVqUYk4xyedQRNfgCRleJSjRaF8E1qyH zrIpFFRFintC+wT5CWN7i4526e4bpuwj5Dzx8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=sGtjiAz9Y2BLsXTL1GINxItJ9npoYiGCTATZNW71kbM=; b=Am9HE8SnkFsNVB6mDu3ynrCFVBdazfzcaLISF+dL2enormFN06P+pFpTnLF7k9jOoa YntU8kLZxceqh8h/uJotA3gF6VMNzoiT+y9sNpXu++EBiXlasDXBXtqNADqyxUGagWFW 2jTLwovrZvYO/iGTsH8iUEokTknu0UZ9QqnM35NyOqVT87UIw3jKyGZZY0qlmlrWeMni wYaZw+LmPwRwbtjZquFPHnBl/7tvM5yJX3EjoqCg+JIhc6eMEfcx8Y9CzdLJXopssfBa jmjAAMNTQw0GeaSmNzu7pnpFowJDCvESLZlcbVQwZOzRFl4qqilVyb/XAA501XhpLpa/ AfLQ== X-Gm-Message-State: AOAM530lC+GdVMy/LVqjChG/uHlbH4IbBRIsZykbC2gJc7GJT5fWhzVN QMluWeGmQaOHUxK42DTLJP7j96BC5JnC4q7qLgxzeDFTQcTagA== X-Google-Smtp-Source: ABdhPJxRuNjD2tp/sF7nztZXonKe9wsWBHIMXqa74bWufvCs3jYizLLemEzp39aPdTcB7tFHHFk20bL4nNx8BoVc6Uw= X-Received: by 2002:a05:6214:cc7:: with SMTP id 7mr13364348qvx.27.1616239371602; Sat, 20 Mar 2021 04:22:51 -0700 (PDT) MIME-Version: 1.0 From: Aditya Prakash Date: Sat, 20 Mar 2021 04:22:41 -0700 Message-ID: To: dm-crypt@saout.de Message-ID-Hash: YTRAWM4VHTDNHE3A5PVWJ2RCVJH7MUOY X-Message-ID-Hash: YTRAWM4VHTDNHE3A5PVWJ2RCVJH7MUOY X-MailFrom: adiprakash@cs.stonybrook.edu X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dm-crypt.saout.de-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.2 Precedence: list Subject: [dm-crypt] [DM-Verity] Corruption after activation during boot List-Id: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: multipart/mixed; boundary="===============1913748386149297740==" --===============1913748386149297740== Content-Type: multipart/alternative; boundary="0000000000009de4b105bdf60db9" --0000000000009de4b105bdf60db9 Content-Type: text/plain; charset="UTF-8" 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. Thanks, Aditya --0000000000009de4b105bdf60db9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
I am using the same device (/dev/sda2) for data an= d 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 activ= ating, 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 s= tuck in the boot loop.

Is there something wrong I = am doing with the hash-offset? Any help or guidance would be really appreci= ated.=C2=A0


Thanks,
Adity= a
--0000000000009de4b105bdf60db9-- --===============1913748386149297740== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dm-crypt mailing list -- dm-crypt@saout.de To unsubscribe send an email to dm-crypt-leave@saout.de --===============1913748386149297740==--