On Mon, 6 Nov 2023, Aaditya Raj Barnwal (QUIC) wrote: > Hi Developers, > > I have attached the patch for file : drivers/md/dm-verity-target.c > > Race condition with some eMMC devices where the early_probe > to dm-verity driver try to check access of data device > fails. As this error is going to impact the bootup and mount > of rootfs. As its impact bootup we make to wait for and > then do a bail-out . > adding the error which show the that dm-init already > ack "all device available " but dm-verity returned > error . > device-mapper: init: all devices available > device-mapper: table: 252:0: verity: Data device lookup failed > device-mapper: ioctl: error adding target to table > > This patch is going to wait based on module parm if not passed it > will be 1sec max. > > This patch is based on > https://lore.kernel.org/lkml/7442e695-654a-59c2-e3dd-710946e6cddd@xxxxxxxx/T/ > which tries to do the same to dm-int level. > > Thanks > Aaditya Hi dm-init already has a parameter "dm-mod.waitfor" that waits for the listed devices. So, you can use "dm-mod.waitfor=/dev/mmcblk0" to wait for the emmc device that you need. Mikulas
