Dear dm-devel:
I encountered the same problem as this one. Is there a solution?
dm-init.c: boot up race with partitions
- From: Steven Walter <steven stevenwalter org>
- To: "dm-devel redhat com" <dm-devel redhat com>
- Subject: dm-init.c: boot up race with partitions
- Date: Mon, 05 Apr 2021 21:38:15 +0000
I am using the dm-mod.create kernel command line parameter to create a verity device at boot. Both the data device and hash device are partitions on an eMMC device. Seemingly at random, the verity device fails to be created at boot because dm_init_init() (and wait_for_device_probe()) returned before the partitions had been scanned:
mmc1: new high speed MMC card at address 0001
device-mapper: table: 253:0: verity: Data device lookup failed
device-mapper: ioctl: error adding target to table
mmcblk1: mmc1:0001 064G30 58.2 GiB
mmcblk1boot0: mmc1:0001 064G30 partition 1 4.00 MiB
mmcblk1boot1: mmc1:0001 064G30 partition 2 4.00 MiB
mmcblk1rpmb: mmc1:0001 064G30 partition 3 4.00 MiB, chardev (247:0)
mmcblk1: p1 p2 p3 p4 p5 p6 p7
I don't see how wait_for_device_probe() knows when partition scanning has been completed. Is this a race or am I missing something?
--
- Steven Walter <steven stevenwalter org>
Sent from ProtonMail, encrypted email based in Switzerland.
声明：这封邮件只允许文件接收者阅读，有很高的机密性要求。禁止其他人使用、打开、复制或转发里面的任何内容。
如果本邮件错误地发给了你，请联系邮件发出者并删除这个文件。机密及法律的特权并不因为误发邮件而放弃或丧失。
任何提出的观点或意见只属于作者的个人见解，并不一定代表理想汽车。
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
