From: Thorsten Glaser <tg@evolvis.org>
To: Max Gautier <mg@max.gautier.name>
Cc: cryptsetup@lists.linux.dev
Subject: Re: dm-integrity: estimate the size needed for separate integrity device
Date: Fri, 10 Jul 2026 19:27:17 +0200 (CEST) [thread overview]
Message-ID: <0eac0c5e-7e2f-a934-8967-8dd9b70a7898@evolvis.org> (raw)
In-Reply-To: <ah05u91w9wfghC8_@framework>
Hi Ma,
>But I'm not sure what size each "integrity tags" partition should be,
>depending on the data device.
I’ve wondered the same.
I extracted some code from the Linux 5.10 kernel (as that’s what I’m
using on bullseye) to estimate that, once for an already created
split-setup device (if you create it too large and want to shrink)
and once before creating.
It assumes defaults for most parameters, but it does support tag size
and sectors per block. Use at your own risk.
https://codeberg.org/mirabilos/useful-scripts/src/branch/master/integritysetup
Thankfully, the kernel refuses to set up the device if the partition
is too small, so you can test.
Here’s to hoping newer kernels/cryptsetup versions don’t break it ;)
bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
prev parent reply other threads:[~2026-07-10 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 7:50 dm-integrity: estimate the size needed for separate integrity device Max Gautier
2026-06-07 13:08 ` Milan Broz
2026-06-08 7:05 ` Max Gautier
2026-07-10 17:27 ` Thorsten Glaser [this message]
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=0eac0c5e-7e2f-a934-8967-8dd9b70a7898@evolvis.org \
--to=tg@evolvis.org \
--cc=cryptsetup@lists.linux.dev \
--cc=mg@max.gautier.name \
/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