Yi Zhang

[udev.log](https://github.com/user-attachments/files/23355003/udev.log) Here is the full udev log during the test.

I downgrade the systemd from systemd-258.1-2.fc44 to systemd-257.10-1.fc42.x86_64, the issue cannot be reproduced now. And the udevadm settle alwasy can be finished within 120s. ``` 109.844s 111.851s 115.309s 111.077s 110.926s...

> Thanks for looking into it. Is the varlink feature new for udevd in v268? If so, the test might trigger a bug? In this case we should get upstream...

> @yizhanglinux Thanks for this PR. With a first look, this test case looks useful for me. I tried to run the test case for a QEMU NVME device on...

I tried 6 NVMe disks with the latest linux-block/for-next and didn't reproduce the WARNING/hang issue, bug there is one intel NVMe SSD, it reports supported lbaf0 to lbaf6, but the...

> @yizhanglinux I guess the failure of nvme/063 indicates a bug in kernel side, and it should be fixed with [this patch](https://lore.kernel.org/linux-nvme/[email protected]/). Could you try it out? Yes, just confirmed...

Here is the `ndctl list` output before the test: ``` [root@storageqe-31 ndctl]# cat ~/dm.dbg [ { "provider":"ACPI.NFIT", "dev":"ndbus1", "scrub_state":"idle", "dimms":[ { "dev":"nmem1", "id":"802c-0f-1730-18311fe3", "handle":17, "phys_id":4359 }, { "dev":"nmem3", "id":"802c-0f-1730-181d9a41", "handle":4113,...

If I run the test suite for the first time after the system boots up, the test case dm.sh can pass, but it fails at the second time. ``` [1/70]...

Hi Alison I already use the ndctl pending branch for the test, btw, the nvdimm I used is nvdimm-n on one DELL server, here is the ndctl output[1]. I tried...

That looks reasonable, both the nvdimm-n and intel nvdimm have the "provider":"ACPI.NFIT", is there a way to distinguish them? If so, we can update the tests to skip on nvdimm-n...