Thread (6 messages) 6 messages, 3 authors, 2022-06-26

Re: [bug report] kmemleak observed from blktests on latest linux-block/for-next

From: Sagi Grimberg <sagi@grimberg.me>
Date: 2022-06-26 14:16:13
Also in: linux-nvme

quoted
quoted
Hi Ming

The kmemleak also can be reproduced on 5.19.0-rc2, pls try to enable
nvme_core multipath and retest.

# cat /sys/module/nvme_core/parameters/multipath
Y
OK, I can understand the reason now since rqos is only removed for blk-mq queue,
then rqos allocated for bio queue is leaked, see disk_release_mq().

The following patch should fix it:
Hi Ming
The kmemleak was fixed by this change, feel free to add

Tested-by: Yi Zhang <redacted>
I just tripped on this myself...
You can add,

Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help