RE: Patch : drivers/md/dm-verity-target.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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;
	}


-----Original Message-----
From: Mikulas Patocka <mpatocka@xxxxxxxxxx> 
Sent: Tuesday, November 14, 2023 8:23 PM
To: Aaditya Raj Barnwal (QUIC) <quic_abarnwal@xxxxxxxxxxx>
Cc: agk@xxxxxxxxxx; snitzer@xxxxxxxxxx; dm-devel@xxxxxxxxxxxxxxx; 
Subject: RE: Patch : drivers/md/dm-verity-target.c

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

On Tue, 14 Nov 2023, Mikulas Patocka wrote:

>
>
> On Fri, 10 Nov 2023, Aaditya Raj Barnwal (QUIC) wrote:
>
> > Hi @Mikulas
> > Sorry for my late reply
> > I was not clear on the ask assuming it to be device configuration , please see below points for your query.
> >
> >  *  Only eMMC chip  Micron product name (S0J35A)  PNM 48(width) CID  
> > value 8GB: 53304A333541h
> >  *  Linux version 5.15.104 compiled for  Arm64 (armv8+ )
>
> I did these commands:
>
> $ git checkout v5.15.104
> $ grep -r 'exiting after' *
>
> and grep didn't find anything. But your log shows an 'exiting after'
> message. So, where does this message 'device-mapper: init:  exiting after'
> come from? Are you using clean v5.15.104 or did you patch the kernel 
> with some external patch?
>
> Mikulas

BTW. I see that the "dm-mod.waitfor" mechanism was introduced in 6.2, and it is not available in 5.15.104.

So I suggest that you upgrade the kernel to at least 6.2, or backport the upstream patch 035641b01e72af4f6c6cf22a4bdb5d7dfc4e8e8e to your kernel 5.15.104.

Mikulas





[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux