From: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@in.bosch.com>
To: "dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: [dm-crypt] Superblock size calculation
Date: Thu, 30 Jan 2020 04:38:36 +0000 [thread overview]
Message-ID: <d85ee80ef7c2dd70fcd8a43f339554bb5296f90c.camel@bosch.com> (raw)
In-Reply-To: <9c428b57-b3e7-38e1-d963-4596e46f69ea@freesources.org>
Hi team,
How to find the superblock size of the physical device which is
encrypted using dm-crypt utility. I have formatted my device using
integritysetup tool and applied integrity using dm-integrity and dm-
crypt stacked on top of that. So my requirement is to corrupt the
physical layer of the device except superblock and check whether it is
mounting successfully.
Note: I tried corrupting the super block (initial some blocks ) and
tried mounting and it fails. so now I have to try without corrupting
any blocks of the superblock and rest of the things I need to corrupt.
The integritysetup dump is giving me the following result.
root@imx8dx_ccu:~# integritysetup dump /dev/mmcblk0p5
Info for integrity device /dev/mmcblk0p5.
superblock_version 1
log2_interleave_sectors 15
integrity_tag_size 32
journal_sections 1
provided_data_sectors 14240
sector_size 512
flags
root@imx8dx_ccu:~#
How to find the superblock size of the device ?
Regards,
Sharmila
next prev parent reply other threads:[~2020-01-30 4:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 14:51 [dm-crypt] how to get keyslog PBKDF settings via libcryptsetup Jonas Meurer
2020-01-29 10:23 ` Ondrej Kozina
2020-01-29 14:14 ` Jonas Meurer
2020-01-29 10:32 ` Ondrej Kozina
2020-01-29 10:36 ` Ondrej Kozina
2020-01-30 4:38 ` EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF) [this message]
2020-01-31 13:52 ` Ondrej Kozina
2020-01-31 13:55 ` Jonas Meurer
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=d85ee80ef7c2dd70fcd8a43f339554bb5296f90c.camel@bosch.com \
--to=external.sharmila.d@in.bosch.com \
--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