Re: [PATCH blktests v2 0/6] nvme: tests for fabrics queue mapping and isolated or offline CPUs

[Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>]

On Nov 04, 2026 / 15:25, Daniel Wagner wrote:
> Connecting an NVMe over Fabrics controller fails or crashes the kernel
> in several cases in current upstream. These tests reproduce each case
> and verify the fix.
> 
> Queue mapping bugs, fixed in mainline:
> 
>   nvme/076  More write and poll queues than online CPUs requested. A
>             queue type got more hardware contexts than online CPUs, a
>             hardware context without CPU failed its Connect command with
>             -EXDEV. Fixed by 99fd0cbae849 ("nvme-fabrics: limit each
>             queue type to the number of online CPUs").
>   nvme/077  No queues left for polling. The poll map kept the default
>             mapping, the queue claimed poll support and polled I/O went
>             to a queue which isn't a poll queue. Fixed by 36ede1aa85d5
>             ("nvme-fabrics: clear the poll map if no poll queues are
>             mapped").
>   nvme/078  Reconnect with fewer I/O queues. Stale io_queues entries
>             mapped the poll queues beyond the hardware contexts and
>             blk_mq_map_swqueue crashed. Fixed by 9588769af5fc
>             ("nvme-fabrics: reset io_queues before computing the queue
>             mapping") and 36ede1aa85d5.

Daniel, thanks for the v2 patch. I applied the first three patches for
the test cases above. Please note that I renumbered them to nvme/078-080.

The other three patches look good. IIUC, they depend on another kernel patch
[*]. I would like to wait for it applied, then take another look on them.

[*] https://lore.kernel.org/linux-block/20261104-nvme-fabrics-isolcpu-v3-1-41953b5dfba0@suse.de/