[bug report] kmemleak observed during blktests nvme-tcp
Yi Zhang
yi.zhang at redhat.com
Thu Apr 20 17:37:13 PDT 2023
Hello
Below kmemleak observed after blktests nvme-tcp, pls help check it, thanks.
commit: linux-block/for-next
aaf9cff31abe (origin/for-next) Merge branch 'for-6.4/io_uring' into for-next
unreferenced object 0xffff88821f0cc880 (size 32):
comm "kworker/1:2H", pid 3067, jiffies 4295825061 (age 12918.254s)
hex dump (first 32 bytes):
82 0c 38 08 00 ea ff ff 00 00 00 00 00 10 00 00 ..8.............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff86f646ab>] __kmalloc+0x4b/0x190
[<ffffffff8776d0bf>] sgl_alloc_order+0x7f/0x360
[<ffffffffc0ba9875>] 0xffffffffc0ba9875
[<ffffffffc0bb068f>] 0xffffffffc0bb068f
[<ffffffffc0bb2038>] 0xffffffffc0bb2038
[<ffffffffc0bb257c>] 0xffffffffc0bb257c
[<ffffffffc0bb2de3>] 0xffffffffc0bb2de3
[<ffffffff86897f49>] process_one_work+0x8b9/0x1550
[<ffffffff8689919c>] worker_thread+0x5ac/0xed0
[<ffffffff868b2222>] kthread+0x2a2/0x340
[<ffffffff866063ac>] ret_from_fork+0x2c/0x50
unreferenced object 0xffff88823abb7c00 (size 512):
comm "nvme", pid 6312, jiffies 4295856007 (age 12887.309s)
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 a0 53 5f 8e ff ff ff ff .........S_.....
backtrace:
[<ffffffff86f63da7>] kmalloc_trace+0x27/0xe0
[<ffffffff87d61205>] device_add+0x645/0x12f0
[<ffffffff871c2a73>] cdev_device_add+0xf3/0x230
[<ffffffffc09ed7c6>] nvme_init_ctrl+0xbe6/0x1140 [nvme_core]
[<ffffffffc0b54e0c>] 0xffffffffc0b54e0c
[<ffffffffc086b177>] 0xffffffffc086b177
[<ffffffffc086b613>] 0xffffffffc086b613
[<ffffffff871b41e6>] vfs_write+0x216/0xc60
[<ffffffff871b5479>] ksys_write+0xf9/0x1d0
[<ffffffff88ba8f9c>] do_syscall_64+0x5c/0x90
[<ffffffff88c000aa>] entry_SYSCALL_64_after_hwframe+0x72/0xdc
unreferenced object 0xffff88810ccc9b80 (size 96):
comm "nvme", pid 6312, jiffies 4295856008 (age 12887.308s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff86f63da7>] kmalloc_trace+0x27/0xe0
[<ffffffff87d918e0>] dev_pm_qos_update_user_latency_tolerance+0xe0/0x200
[<ffffffffc09ed83c>] nvme_init_ctrl+0xc5c/0x1140 [nvme_core]
[<ffffffffc0b54e0c>] 0xffffffffc0b54e0c
[<ffffffffc086b177>] 0xffffffffc086b177
[<ffffffffc086b613>] 0xffffffffc086b613
[<ffffffff871b41e6>] vfs_write+0x216/0xc60
[<ffffffff871b5479>] ksys_write+0xf9/0x1d0
[<ffffffff88ba8f9c>] do_syscall_64+0x5c/0x90
[<ffffffff88c000aa>] entry_SYSCALL_64_after_hwframe+0x72/0xdc
unreferenced object 0xffff8881d1fdb780 (size 64):
comm "check", pid 6358, jiffies 4295859851 (age 12883.466s)
hex dump (first 32 bytes):
44 48 48 43 2d 31 3a 30 30 3a 4e 46 76 44 6d 75 DHHC-1:00:NFvDmu
52 58 77 79 54 79 62 57 78 70 43 4a 45 4a 68 36 RXwyTybWxpCJEJh6
backtrace:
[<ffffffff86f646ab>] __kmalloc+0x4b/0x190
[<ffffffffc09fb710>] nvme_ctrl_dhchap_secret_store+0x110/0x350 [nvme_core]
[<ffffffff873cc848>] kernfs_fop_write_iter+0x358/0x530
[<ffffffff871b47d2>] vfs_write+0x802/0xc60
[<ffffffff871b5479>] ksys_write+0xf9/0x1d0
[<ffffffff88ba8f9c>] do_syscall_64+0x5c/0x90
[<ffffffff88c000aa>] entry_SYSCALL_64_after_hwframe+0x72/0xdc
unreferenced object 0xffff8881d1fdb600 (size 64):
comm "check", pid 6358, jiffies 4295859908 (age 12883.409s)
hex dump (first 32 bytes):
44 48 48 43 2d 31 3a 30 30 3a 4e 46 76 44 6d 75 DHHC-1:00:NFvDmu
52 58 77 79 54 79 62 57 78 70 43 4a 45 4a 68 36 RXwyTybWxpCJEJh6
backtrace:
[<ffffffff86f646ab>] __kmalloc+0x4b/0x190
[<ffffffffc09fb710>] nvme_ctrl_dhchap_secret_store+0x110/0x350 [nvme_core]
[<ffffffff873cc848>] kernfs_fop_write_iter+0x358/0x530
[<ffffffff871b47d2>] vfs_write+0x802/0xc60
[<ffffffff871b5479>] ksys_write+0xf9/0x1d0
[<ffffffff88ba8f9c>] do_syscall_64+0x5c/0x90
[<ffffffff88c000aa>] entry_SYSCALL_64_after_hwframe+0x72/0xdc
--
Best Regards,
Yi Zhang
More information about the Linux-nvme
mailing list