On Mon, 31 Oct 2022 03:12:42 +0000, Chen Jun wrote:
> There is a kmemleak caused by modprobe null_blk.ko
>
> unreferenced object 0xffff8881acb1f000 (size 1024):
> comm "modprobe", pid 836, jiffies 4294971190 (age 27.068s)
> hex dump (first 32 bytes):
> 00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........
> ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff .........S......
> backtrace:
> [<000000004a10c249>] kmalloc_node_trace+0x22/0x60
> [<00000000648f7950>] blk_mq_alloc_and_init_hctx+0x289/0x350
> [<00000000af06de0e>] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
> [<00000000e00c1872>] blk_mq_init_allocated_queue+0x48c/0x1440
> [<00000000d16b4e68>] __blk_mq_alloc_disk+0xc8/0x1c0
> [<00000000d10c98c3>] 0xffffffffc450d69d
> [<00000000b9299f48>] 0xffffffffc4538392
> [<0000000061c39ed6>] do_one_initcall+0xd0/0x4f0
> [<00000000b389383b>] do_init_module+0x1a4/0x680
> [<0000000087cf3542>] load_module+0x6249/0x7110
> [<00000000beba61b8>] __do_sys_finit_module+0x140/0x200
> [<00000000fdcfff51>] do_syscall_64+0x35/0x80
> [<000000003c0f1f71>] entry_SYSCALL_64_after_hwframe+0x46/0xb0
>
> [...]
Applied, thanks!
[1/1] blk-mq: Fix kmemleak in blk_mq_init_allocated_queue
commit: 943f45b9399ed8b2b5190cbc797995edaa97f58f
Best regards,
--
Jens Axboe
