On Wed, Nov 15 2023 at 2:01P -0500,
Aaditya Raj Barnwal <abarnwal@xxxxxxxxxxxxxxxx> wrote:
> Sorry if that statement confused you , It was debugging print
> that was added to check if the tight while loop has ended or not
>
> Code : dm-init.c
> dm_init_init()
>
> wait_for_device_probe();
> for (i = 0; i < ARRAY_SIZE(waitfor); i++) {
> if (waitfor[i]) {
> dev_t dev;
>
> DMERR("waiting for device %s ...", waitfor[i]);
> while ((dev= name_to_dev_t(waitfor[i]) !=0))
> fsleep(5000);
> }
>
> DMERR("exiting after %s ",waitfor[i]); <<<<<<<<<<<here it was added
> }
>
> if (waitfor[0])
> DMINFO("all devices available");
>
> list_for_each_entry(dev, &devices, list) {
> if (dm_early_create(&dev->dmi, dev->table,
> dev->target_args_array))
> break;
> }
>
Mikulas wasn't confused. He was pointing out that you have made
changes to your kernel without sharing what they are.
But your issue is that you configured the dm-mod.waitfor device
incorrectly. You must wait for the underlying physical device(s) that
the virtual DM device depends on.
Mike
