[pkg-cryptsetup-devel] Bug#639832: cryptsetup: initramfs hooks vs aesni-intel

[Simon Mackinlay]

Actually this may be more serious than it first seems.

A typical* user might have...

FS (say, ext4) stacked on LV stacked on VG stacked on PV stacked on dm-crypt blockdev stacked on partition (a reasonably common/ recommended deployment, TRIM issues notwithstanding).


In this case - the arch-specific crypto module may not have loaded (same as it is not loaded for root or swap blockdevs in the reported bug) - but the impact is more severe, in that _no_ LV (hence no FS) will utilise arch-specific HW crypto modules.


* nb: this design (lvm2 on dm-crypt) was exactly the design I started with; I only shifted to ...

FS stacked on dm-crypt stacked on partition

... in order to help triage this problem.