From: JeongHyeon Lee <jhs2.lee@samsung.com>
To: snitzer@redhat.com
Cc: agk@redhat.com, dm-devel@redhat.com,
linux-kernel@vger.kernel.org,
JeongHyeon Lee <jhs2.lee@samsung.com>
Subject: [PATCH 1/2] dm verity: fix DM_VERITY_OPTS_MAX value
Date: Thu, 11 Mar 2021 21:10:50 +0900 [thread overview]
Message-ID: <1615464651-23675-1-git-send-email-jhs2.lee@samsung.com> (raw)
In-Reply-To: <CGME20210311121838epcas1p295d765b3c89ddacac9cd9bbf918d6345@epcas1p2.samsung.com>
Three optional parameters at once using dm verity table is not
supported, option can only be used exclusively.
e.g.)
(verity_mode) (ignore_zero_block) (check_at_most_once)
verity table: '1 /dev/sdb /dev/sdb 4096 4096 1028807 1028807
<hash_alg> <root_hash> <salt> 11 use_fec_from_device /dev/sdb
fec_roots 2 fec_blocks 1036909 fec_start 1036909
restart_on_corruption ignore_zero_blocks check_at_most_once'
Signed-off-by: JeongHyeon Lee <jhs2.lee@samsung.com>
---
drivers/md/dm-verity-target.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/md/dm-verity-target.c b/drivers/md/dm-verity-target.c
index 6b8e5bdd8526..808a98ef624c 100644
--- a/drivers/md/dm-verity-target.c
+++ b/drivers/md/dm-verity-target.c
@@ -34,7 +34,7 @@
#define DM_VERITY_OPT_IGN_ZEROES "ignore_zero_blocks"
#define DM_VERITY_OPT_AT_MOST_ONCE "check_at_most_once"
-#define DM_VERITY_OPTS_MAX (2 + DM_VERITY_OPTS_FEC + \
+#define DM_VERITY_OPTS_MAX (3 + DM_VERITY_OPTS_FEC + \
DM_VERITY_ROOT_HASH_VERIFICATION_OPTS)
static unsigned dm_verity_prefetch_cluster = DM_VERITY_DEFAULT_PREFETCH_SIZE;
--
2.17.1
next parent reply other threads:[~2021-03-11 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210311121838epcas1p295d765b3c89ddacac9cd9bbf918d6345@epcas1p2.samsung.com>
2021-03-11 12:10 ` JeongHyeon Lee [this message]
[not found] ` <CGME20210311121850epcas1p493c255a586998916febfebaf994bc5dc@epcas1p4.samsung.com>
2021-03-11 12:10 ` [PATCH 2/2] dm verity: allow only one verify mode JeongHyeon Lee
2021-03-11 22:34 ` Sami Tolvanen
2021-03-12 7:04 ` 이정현
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=1615464651-23675-1-git-send-email-jhs2.lee@samsung.com \
--to=jhs2.lee@samsung.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.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
all inboxes | Powered by JetHome®