We're now opening the LUKS device using the master key directly and the crash is happening again in both the original 4.15.0-54-generic (buildd@lgw01-amd64-014) kernel or the patched 4.15.0-54-generic (arighi@kathleen) kernel. The backtrace is very similar but unlike the previous scenario it happens even if delays as large as 5000 ms are placed between partition table re-reading and commands.
The LUKS device is created and accessed using the following commands:
We're now opening the LUKS device using the master key directly and the crash is happening again in both the original 4.15.0-54-generic (buildd@ lgw01-amd64- 014) kernel or the patched 4.15.0-54-generic (arighi@kathleen) kernel. The backtrace is very similar but unlike the previous scenario it happens even if delays as large as 5000 ms are placed between partition table re-reading and commands.
The LUKS device is created and accessed using the following commands:
# cryptsetup -q luksFormat --type luks2 --pbkdf-memory 10000 --master-key-file <keyfile> <device>
# LD_PRELOAD= /lib/no- udev.so cryptsetup open --master-key-file <keyfile> <device> <name>