nvme-multipath: fix lockdep WARN due to partition scan work
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
a91b7eddf45afeeb9c5ece11dddff5de0921b00f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvme-multipath: fix lockdep WARN due to partition scan work
Blktests test cases nvme/014, 057 and 058 fail occasionally due to a lockdep WARN. As reported in the Closes tag URL, the WARN indicates that a deadlock can happen due to the dependency among disk->open_mutex, kblockd workqueue completion and partition_scan_work completion.
To avoid the lockdep WARN and the potential deadlock, cut the dependency by running the partition_scan_work not by kblockd workqueue but by nvme_wq.
From the CVE record · Linux
In the Linux kernel, NVMe multipath partition scanning can create a workqueue dependency that triggers a lockdep warning and may cause a deadlock. The input does not describe an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with NVMe multipath should check their kernel versions; affected versions are not specified.