Hi all, as written in the subject we do see an odd dm-integrity behaviour during the journal replay step. First things first, a short introduction to our setup: - Linux v6.8 - We do have a dm-integrity+dm-crypt setup to provide an authenticated encrypted ext4-based rw data partition. - The setup is done with a custom script [1] since we are making use of the kernel trusted-keys infrastructure which isn't supported by LUKS2 at the moment. - The device has no power failsafe e.g. hard power-cuts can appear. Therefore we use the dm-integrity J(ournal) mode. - The storage backend is an eMMC with 512Byte block size. - We use the dm-integrity 4K block size option to reduce the tag/metadata overhead.
