* [bug report]nvmet_auth kmemleak observed during blktests
@ 2026-04-03 8:46 Yi Zhang
2026-04-03 9:21 ` Maurizio Lombardi
0 siblings, 1 reply; 4+ messages in thread
From: Yi Zhang @ 2026-04-03 8:46 UTC (permalink / raw)
To: linux-block, open list:NVM EXPRESS DRIVER; +Cc: Shinichiro Kawasaki
Hi
I found the following kmemleak during blktests on the
linux-block/for-next, please help check it and let me know if you need
any test/info for it, thanks.
commit:
aac56c7b77fa (HEAD -> for-next, origin/for-next) Merge branch
'for-7.1/io_uring' into for-next
reproducer:
nvme_trtype=loop ./check nvme/041 nvme/042 nvme/043 nvme/044 nvme/045
nvme/051 nvme/052
kmemleak:
unreferenced object 0xff11000305c48240 (size 32):
comm "kworker/u48:3", pid 123223, jiffies 4401374163
hex dump (first 32 bytes):
30 1e 78 66 9b 04 e7 4a d5 d7 a3 a2 ab 1f f1 22 0.xf...J......."
11 4a aa 11 b5 f7 fa f6 24 a6 17 11 e6 f8 e7 dc .J......$.......
backtrace (crc 58405ce8):
__kmalloc_noprof+0x635/0x870
nvmet_auth_challenge+0x329/0x9f0 [nvmet]
nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff1100027be14c00 (size 256):
comm "kworker/u48:3", pid 123223, jiffies 4401374168
hex dump (first 32 bytes):
30 96 ec 83 33 bb fc 41 ec 81 70 14 1e ad 32 fd 0...3..A..p...2.
39 b8 ca 9c 99 22 ff 28 f0 80 f3 e0 1d 82 36 a9 9....".(......6.
backtrace (crc e365275d):
__kmalloc_noprof+0x635/0x870
nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
nvmet_auth_reply+0x436/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000305c48d40 (size 32):
comm "kworker/u48:3", pid 123223, jiffies 4401374170
hex dump (first 32 bytes):
c0 8b 24 c4 c1 5a 37 d1 fc 49 ec 3e 44 05 7e 19 ..$..Z7..I.>D.~.
70 39 6a d0 53 22 6d 23 fc b9 94 83 e3 3a 60 e2 p9j.S"m#.....:`.
backtrace (crc 8284cf12):
__kmalloc_node_track_caller_noprof+0x637/0x880
kmemdup_noprof+0x22/0x50
nvmet_auth_reply+0x2ba/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff1100016dd8c7c0 (size 32):
comm "kworker/u48:2", pid 139664, jiffies 4401374600
hex dump (first 32 bytes):
21 1e e5 a0 b9 e6 a0 6b 85 cb 62 ff 30 d6 21 0f !......k..b.0.!.
05 89 bc 6a 44 fe 2a c4 bd 35 23 59 6c 56 2b 2e ...jD.*..5#YlV+.
backtrace (crc e32fd56c):
__kmalloc_noprof+0x635/0x870
nvmet_auth_challenge+0x329/0x9f0 [nvmet]
nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000255549600 (size 256):
comm "kworker/u48:2", pid 139664, jiffies 4401374604
hex dump (first 32 bytes):
11 1a 6e 99 d1 bc ae 48 5d aa f1 74 62 30 68 c4 ..n....H]..tb0h.
07 9f 31 dc 83 a4 a4 92 47 18 9c 04 1e 7d 68 c1 ..1.....G....}h.
backtrace (crc db3ad817):
__kmalloc_noprof+0x635/0x870
nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
nvmet_auth_reply+0x436/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff1100016dd8cc00 (size 32):
comm "kworker/u48:2", pid 139664, jiffies 4401374609
hex dump (first 32 bytes):
51 ff e9 8e 10 6b b4 b3 3f 6c 7d f2 74 eb 42 98 Q....k..?l}.t.B.
6c f8 ab ec 10 d6 e8 0f 02 79 4a e4 ec b2 ce ed l........yJ.....
backtrace (crc 7099040d):
__kmalloc_node_track_caller_noprof+0x637/0x880
kmemdup_noprof+0x22/0x50
nvmet_auth_reply+0x2ba/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff1100025554a800 (size 256):
comm "kworker/u48:2", pid 139664, jiffies 4401374633
hex dump (first 32 bytes):
eb a9 ed 0e b7 42 c6 6c 48 ee 56 29 a4 8a 99 18 .....B.lH.V)....
1c 90 2a 53 22 7a ee 5a c0 6e 60 43 5b 33 a1 d2 ..*S"z.Z.n`C[3..
backtrace (crc 3ce24e58):
__kmalloc_noprof+0x635/0x870
nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
nvmet_auth_reply+0x436/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000267237a80 (size 32):
comm "kworker/u48:2", pid 139664, jiffies 4401374635
hex dump (first 32 bytes):
20 25 77 95 60 f2 19 5a 09 20 2c 25 8b 04 2a 4b %w.`..Z. ,%..*K
b9 53 8e 10 39 b9 07 0d e0 fc 93 3f 82 50 86 0c .S..9......?.P..
backtrace (crc 3f42440d):
__kmalloc_node_track_caller_noprof+0x637/0x880
kmemdup_noprof+0x22/0x50
nvmet_auth_reply+0x2ba/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000138f46e40 (size 32):
comm "kworker/u48:2", pid 139664, jiffies 4401374654
hex dump (first 32 bytes):
2d da 99 66 3b e7 d6 65 aa d7 1f a6 51 b4 ab 19 -..f;..e....Q...
46 d7 30 0d 12 fd 55 90 c4 6a 4a 7a b8 55 7f 4f F.0...U..jJz.U.O
backtrace (crc 3ab35d56):
__kmalloc_noprof+0x635/0x870
nvmet_auth_challenge+0x329/0x9f0 [nvmet]
nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000126860400 (size 256):
comm "kworker/u48:2", pid 139664, jiffies 4401374658
hex dump (first 32 bytes):
cb 48 8c 49 58 82 bd fd 21 5b e4 a5 5b 5e 7b 8b .H.IX...![..[^{.
48 6a 47 3e 9f b7 76 06 c8 47 6a 5f 3e b4 20 15 HjG>..v..Gj_>. .
backtrace (crc b164cda1):
__kmalloc_noprof+0x635/0x870
nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
nvmet_auth_reply+0x436/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000138f468c0 (size 32):
comm "kworker/u48:2", pid 139664, jiffies 4401374662
hex dump (first 32 bytes):
01 dd af 3b af a0 f8 ec 61 80 c4 aa ad 56 9a 27 ...;....a....V.'
d4 f9 f9 8d 98 64 ce 5a 81 e2 14 e0 e3 5c 79 97 .....d.Z.....\y.
backtrace (crc b24f43c2):
__kmalloc_node_track_caller_noprof+0x637/0x880
kmemdup_noprof+0x22/0x50
nvmet_auth_reply+0x2ba/0xd00 [nvmet]
nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
unreferenced object 0xff11000185c80580 (size 64):
comm "kworker/u48:2", pid 139664, jiffies 4401374716
hex dump (first 32 bytes):
bf a4 73 5a 5c a7 d7 8e f7 6e f9 39 3a 94 66 a4 ..sZ\....n.9:.f.
8e f9 bc f6 9a 23 ac dc c8 71 85 ef 09 4c ac 38 .....#...q...L.8
backtrace (crc 70f5e8bf):
__kmalloc_noprof+0x635/0x870
nvmet_auth_challenge+0x329/0x9f0 [nvmet]
nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
process_one_work+0xd98/0x1390
worker_thread+0x60b/0x1000
kthread+0x36c/0x470
ret_from_fork+0x5dc/0x8e0
ret_from_fork_asm+0x1a/0x30
--
Best Regards,
Yi Zhang
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bug report]nvmet_auth kmemleak observed during blktests
2026-04-03 8:46 [bug report]nvmet_auth kmemleak observed during blktests Yi Zhang
@ 2026-04-03 9:21 ` Maurizio Lombardi
2026-04-07 0:54 ` Yi Zhang
0 siblings, 1 reply; 4+ messages in thread
From: Maurizio Lombardi @ 2026-04-03 9:21 UTC (permalink / raw)
To: Yi Zhang, linux-block, open list:NVM EXPRESS DRIVER; +Cc: Shinichiro Kawasaki
On Fri Apr 3, 2026 at 10:46 AM CEST, Yi Zhang wrote:
> Hi
>
> I found the following kmemleak during blktests on the
> linux-block/for-next, please help check it and let me know if you need
> any test/info for it, thanks.
>
> commit:
> aac56c7b77fa (HEAD -> for-next, origin/for-next) Merge branch
> 'for-7.1/io_uring' into for-next
>
> reproducer:
> nvme_trtype=loop ./check nvme/041 nvme/042 nvme/043 nvme/044 nvme/045
> nvme/051 nvme/052
>
> kmemleak:
> unreferenced object 0xff11000305c48240 (size 32):
> comm "kworker/u48:3", pid 123223, jiffies 4401374163
> hex dump (first 32 bytes):
> 30 1e 78 66 9b 04 e7 4a d5 d7 a3 a2 ab 1f f1 22 0.xf...J......."
> 11 4a aa 11 b5 f7 fa f6 24 a6 17 11 e6 f8 e7 dc .J......$.......
> backtrace (crc 58405ce8):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
Maybe this has been introduced by commit 2e6eb6b277f5
("nvmet-tcp: Don't free SQ on authentication success")
If nvmet_execute_auth_receive() gets called twice and executes
nvmet_auth_challenge(), the dhchap_c1 pointer is leaked.
Maurizio
> unreferenced object 0xff1100027be14c00 (size 256):
> comm "kworker/u48:3", pid 123223, jiffies 4401374168
> hex dump (first 32 bytes):
> 30 96 ec 83 33 bb fc 41 ec 81 70 14 1e ad 32 fd 0...3..A..p...2.
> 39 b8 ca 9c 99 22 ff 28 f0 80 f3 e0 1d 82 36 a9 9....".(......6.
> backtrace (crc e365275d):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> nvmet_auth_reply+0x436/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000305c48d40 (size 32):
> comm "kworker/u48:3", pid 123223, jiffies 4401374170
> hex dump (first 32 bytes):
> c0 8b 24 c4 c1 5a 37 d1 fc 49 ec 3e 44 05 7e 19 ..$..Z7..I.>D.~.
> 70 39 6a d0 53 22 6d 23 fc b9 94 83 e3 3a 60 e2 p9j.S"m#.....:`.
> backtrace (crc 8284cf12):
> __kmalloc_node_track_caller_noprof+0x637/0x880
> kmemdup_noprof+0x22/0x50
> nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff1100016dd8c7c0 (size 32):
> comm "kworker/u48:2", pid 139664, jiffies 4401374600
> hex dump (first 32 bytes):
> 21 1e e5 a0 b9 e6 a0 6b 85 cb 62 ff 30 d6 21 0f !......k..b.0.!.
> 05 89 bc 6a 44 fe 2a c4 bd 35 23 59 6c 56 2b 2e ...jD.*..5#YlV+.
> backtrace (crc e32fd56c):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000255549600 (size 256):
> comm "kworker/u48:2", pid 139664, jiffies 4401374604
> hex dump (first 32 bytes):
> 11 1a 6e 99 d1 bc ae 48 5d aa f1 74 62 30 68 c4 ..n....H]..tb0h.
> 07 9f 31 dc 83 a4 a4 92 47 18 9c 04 1e 7d 68 c1 ..1.....G....}h.
> backtrace (crc db3ad817):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> nvmet_auth_reply+0x436/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff1100016dd8cc00 (size 32):
> comm "kworker/u48:2", pid 139664, jiffies 4401374609
> hex dump (first 32 bytes):
> 51 ff e9 8e 10 6b b4 b3 3f 6c 7d f2 74 eb 42 98 Q....k..?l}.t.B.
> 6c f8 ab ec 10 d6 e8 0f 02 79 4a e4 ec b2 ce ed l........yJ.....
> backtrace (crc 7099040d):
> __kmalloc_node_track_caller_noprof+0x637/0x880
> kmemdup_noprof+0x22/0x50
> nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff1100025554a800 (size 256):
> comm "kworker/u48:2", pid 139664, jiffies 4401374633
> hex dump (first 32 bytes):
> eb a9 ed 0e b7 42 c6 6c 48 ee 56 29 a4 8a 99 18 .....B.lH.V)....
> 1c 90 2a 53 22 7a ee 5a c0 6e 60 43 5b 33 a1 d2 ..*S"z.Z.n`C[3..
> backtrace (crc 3ce24e58):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> nvmet_auth_reply+0x436/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000267237a80 (size 32):
> comm "kworker/u48:2", pid 139664, jiffies 4401374635
> hex dump (first 32 bytes):
> 20 25 77 95 60 f2 19 5a 09 20 2c 25 8b 04 2a 4b %w.`..Z. ,%..*K
> b9 53 8e 10 39 b9 07 0d e0 fc 93 3f 82 50 86 0c .S..9......?.P..
> backtrace (crc 3f42440d):
> __kmalloc_node_track_caller_noprof+0x637/0x880
> kmemdup_noprof+0x22/0x50
> nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000138f46e40 (size 32):
> comm "kworker/u48:2", pid 139664, jiffies 4401374654
> hex dump (first 32 bytes):
> 2d da 99 66 3b e7 d6 65 aa d7 1f a6 51 b4 ab 19 -..f;..e....Q...
> 46 d7 30 0d 12 fd 55 90 c4 6a 4a 7a b8 55 7f 4f F.0...U..jJz.U.O
> backtrace (crc 3ab35d56):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000126860400 (size 256):
> comm "kworker/u48:2", pid 139664, jiffies 4401374658
> hex dump (first 32 bytes):
> cb 48 8c 49 58 82 bd fd 21 5b e4 a5 5b 5e 7b 8b .H.IX...![..[^{.
> 48 6a 47 3e 9f b7 76 06 c8 47 6a 5f 3e b4 20 15 HjG>..v..Gj_>. .
> backtrace (crc b164cda1):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> nvmet_auth_reply+0x436/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000138f468c0 (size 32):
> comm "kworker/u48:2", pid 139664, jiffies 4401374662
> hex dump (first 32 bytes):
> 01 dd af 3b af a0 f8 ec 61 80 c4 aa ad 56 9a 27 ...;....a....V.'
> d4 f9 f9 8d 98 64 ce 5a 81 e2 14 e0 e3 5c 79 97 .....d.Z.....\y.
> backtrace (crc b24f43c2):
> __kmalloc_node_track_caller_noprof+0x637/0x880
> kmemdup_noprof+0x22/0x50
> nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xff11000185c80580 (size 64):
> comm "kworker/u48:2", pid 139664, jiffies 4401374716
> hex dump (first 32 bytes):
> bf a4 73 5a 5c a7 d7 8e f7 6e f9 39 3a 94 66 a4 ..sZ\....n.9:.f.
> 8e f9 bc f6 9a 23 ac dc c8 71 85 ef 09 4c ac 38 .....#...q...L.8
> backtrace (crc 70f5e8bf):
> __kmalloc_noprof+0x635/0x870
> nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> process_one_work+0xd98/0x1390
> worker_thread+0x60b/0x1000
> kthread+0x36c/0x470
> ret_from_fork+0x5dc/0x8e0
> ret_from_fork_asm+0x1a/0x30
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bug report]nvmet_auth kmemleak observed during blktests
2026-04-03 9:21 ` Maurizio Lombardi
@ 2026-04-07 0:54 ` Yi Zhang
2026-04-07 1:23 ` Alistair Francis
0 siblings, 1 reply; 4+ messages in thread
From: Yi Zhang @ 2026-04-07 0:54 UTC (permalink / raw)
To: Maurizio Lombardi, Alistair Francis
Cc: linux-block, open list:NVM EXPRESS DRIVER, Shinichiro Kawasaki,
Christoph Hellwig, Hannes Reinecke, wilfred.mallawa,
Sagi Grimberg, Keith Busch
On Fri, Apr 3, 2026 at 5:21 PM Maurizio Lombardi <mlombard@arkamax.eu> wrote:
>
> On Fri Apr 3, 2026 at 10:46 AM CEST, Yi Zhang wrote:
> > Hi
> >
> > I found the following kmemleak during blktests on the
> > linux-block/for-next, please help check it and let me know if you need
> > any test/info for it, thanks.
> >
> > commit:
> > aac56c7b77fa (HEAD -> for-next, origin/for-next) Merge branch
> > 'for-7.1/io_uring' into for-next
> >
> > reproducer:
> > nvme_trtype=loop ./check nvme/041 nvme/042 nvme/043 nvme/044 nvme/045
> > nvme/051 nvme/052
> >
> > kmemleak:
> > unreferenced object 0xff11000305c48240 (size 32):
> > comm "kworker/u48:3", pid 123223, jiffies 4401374163
> > hex dump (first 32 bytes):
> > 30 1e 78 66 9b 04 e7 4a d5 d7 a3 a2 ab 1f f1 22 0.xf...J......."
> > 11 4a aa 11 b5 f7 fa f6 24 a6 17 11 e6 f8 e7 dc .J......$.......
> > backtrace (crc 58405ce8):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
>
> Maybe this has been introduced by commit 2e6eb6b277f5
> ("nvmet-tcp: Don't free SQ on authentication success")
>
> If nvmet_execute_auth_receive() gets called twice and executes
> nvmet_auth_challenge(), the dhchap_c1 pointer is leaked.
Thanks Maurizio.
The kmemleak cannot be reproduced now after reverting that commit.
>
> Maurizio
>
> > unreferenced object 0xff1100027be14c00 (size 256):
> > comm "kworker/u48:3", pid 123223, jiffies 4401374168
> > hex dump (first 32 bytes):
> > 30 96 ec 83 33 bb fc 41 ec 81 70 14 1e ad 32 fd 0...3..A..p...2.
> > 39 b8 ca 9c 99 22 ff 28 f0 80 f3 e0 1d 82 36 a9 9....".(......6.
> > backtrace (crc e365275d):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000305c48d40 (size 32):
> > comm "kworker/u48:3", pid 123223, jiffies 4401374170
> > hex dump (first 32 bytes):
> > c0 8b 24 c4 c1 5a 37 d1 fc 49 ec 3e 44 05 7e 19 ..$..Z7..I.>D.~.
> > 70 39 6a d0 53 22 6d 23 fc b9 94 83 e3 3a 60 e2 p9j.S"m#.....:`.
> > backtrace (crc 8284cf12):
> > __kmalloc_node_track_caller_noprof+0x637/0x880
> > kmemdup_noprof+0x22/0x50
> > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff1100016dd8c7c0 (size 32):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374600
> > hex dump (first 32 bytes):
> > 21 1e e5 a0 b9 e6 a0 6b 85 cb 62 ff 30 d6 21 0f !......k..b.0.!.
> > 05 89 bc 6a 44 fe 2a c4 bd 35 23 59 6c 56 2b 2e ...jD.*..5#YlV+.
> > backtrace (crc e32fd56c):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000255549600 (size 256):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374604
> > hex dump (first 32 bytes):
> > 11 1a 6e 99 d1 bc ae 48 5d aa f1 74 62 30 68 c4 ..n....H]..tb0h.
> > 07 9f 31 dc 83 a4 a4 92 47 18 9c 04 1e 7d 68 c1 ..1.....G....}h.
> > backtrace (crc db3ad817):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff1100016dd8cc00 (size 32):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374609
> > hex dump (first 32 bytes):
> > 51 ff e9 8e 10 6b b4 b3 3f 6c 7d f2 74 eb 42 98 Q....k..?l}.t.B.
> > 6c f8 ab ec 10 d6 e8 0f 02 79 4a e4 ec b2 ce ed l........yJ.....
> > backtrace (crc 7099040d):
> > __kmalloc_node_track_caller_noprof+0x637/0x880
> > kmemdup_noprof+0x22/0x50
> > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff1100025554a800 (size 256):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374633
> > hex dump (first 32 bytes):
> > eb a9 ed 0e b7 42 c6 6c 48 ee 56 29 a4 8a 99 18 .....B.lH.V)....
> > 1c 90 2a 53 22 7a ee 5a c0 6e 60 43 5b 33 a1 d2 ..*S"z.Z.n`C[3..
> > backtrace (crc 3ce24e58):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000267237a80 (size 32):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374635
> > hex dump (first 32 bytes):
> > 20 25 77 95 60 f2 19 5a 09 20 2c 25 8b 04 2a 4b %w.`..Z. ,%..*K
> > b9 53 8e 10 39 b9 07 0d e0 fc 93 3f 82 50 86 0c .S..9......?.P..
> > backtrace (crc 3f42440d):
> > __kmalloc_node_track_caller_noprof+0x637/0x880
> > kmemdup_noprof+0x22/0x50
> > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000138f46e40 (size 32):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374654
> > hex dump (first 32 bytes):
> > 2d da 99 66 3b e7 d6 65 aa d7 1f a6 51 b4 ab 19 -..f;..e....Q...
> > 46 d7 30 0d 12 fd 55 90 c4 6a 4a 7a b8 55 7f 4f F.0...U..jJz.U.O
> > backtrace (crc 3ab35d56):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000126860400 (size 256):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374658
> > hex dump (first 32 bytes):
> > cb 48 8c 49 58 82 bd fd 21 5b e4 a5 5b 5e 7b 8b .H.IX...![..[^{.
> > 48 6a 47 3e 9f b7 76 06 c8 47 6a 5f 3e b4 20 15 HjG>..v..Gj_>. .
> > backtrace (crc b164cda1):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000138f468c0 (size 32):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374662
> > hex dump (first 32 bytes):
> > 01 dd af 3b af a0 f8 ec 61 80 c4 aa ad 56 9a 27 ...;....a....V.'
> > d4 f9 f9 8d 98 64 ce 5a 81 e2 14 e0 e3 5c 79 97 .....d.Z.....\y.
> > backtrace (crc b24f43c2):
> > __kmalloc_node_track_caller_noprof+0x637/0x880
> > kmemdup_noprof+0x22/0x50
> > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
> > unreferenced object 0xff11000185c80580 (size 64):
> > comm "kworker/u48:2", pid 139664, jiffies 4401374716
> > hex dump (first 32 bytes):
> > bf a4 73 5a 5c a7 d7 8e f7 6e f9 39 3a 94 66 a4 ..sZ\....n.9:.f.
> > 8e f9 bc f6 9a 23 ac dc c8 71 85 ef 09 4c ac 38 .....#...q...L.8
> > backtrace (crc 70f5e8bf):
> > __kmalloc_noprof+0x635/0x870
> > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > process_one_work+0xd98/0x1390
> > worker_thread+0x60b/0x1000
> > kthread+0x36c/0x470
> > ret_from_fork+0x5dc/0x8e0
> > ret_from_fork_asm+0x1a/0x30
>
--
Best Regards,
Yi Zhang
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bug report]nvmet_auth kmemleak observed during blktests
2026-04-07 0:54 ` Yi Zhang
@ 2026-04-07 1:23 ` Alistair Francis
0 siblings, 0 replies; 4+ messages in thread
From: Alistair Francis @ 2026-04-07 1:23 UTC (permalink / raw)
To: yi.zhang@redhat.com, mlombard@arkamax.eu
Cc: hch@lst.de, sagi@grimberg.me, hare@suse.de,
linux-nvme@lists.infradead.org, Shinichiro Kawasaki,
Wilfred Mallawa, linux-block@vger.kernel.org, kbusch@kernel.org
On Tue, 2026-04-07 at 08:54 +0800, Yi Zhang wrote:
> On Fri, Apr 3, 2026 at 5:21 PM Maurizio Lombardi
> <mlombard@arkamax.eu> wrote:
> >
> > On Fri Apr 3, 2026 at 10:46 AM CEST, Yi Zhang wrote:
> > > Hi
> > >
> > > I found the following kmemleak during blktests on the
> > > linux-block/for-next, please help check it and let me know if you
> > > need
> > > any test/info for it, thanks.
> > >
> > > commit:
> > > aac56c7b77fa (HEAD -> for-next, origin/for-next) Merge branch
> > > 'for-7.1/io_uring' into for-next
> > >
> > > reproducer:
> > > nvme_trtype=loop ./check nvme/041 nvme/042 nvme/043 nvme/044
> > > nvme/045
> > > nvme/051 nvme/052
> > >
> > > kmemleak:
> > > unreferenced object 0xff11000305c48240 (size 32):
> > > comm "kworker/u48:3", pid 123223, jiffies 4401374163
> > > hex dump (first 32 bytes):
> > > 30 1e 78 66 9b 04 e7 4a d5 d7 a3 a2 ab 1f f1 22
> > > 0.xf...J......."
> > > 11 4a aa 11 b5 f7 fa f6 24 a6 17 11 e6 f8 e7 dc
> > > .J......$.......
> > > backtrace (crc 58405ce8):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> >
> > Maybe this has been introduced by commit 2e6eb6b277f5
> > ("nvmet-tcp: Don't free SQ on authentication success")
> >
> > If nvmet_execute_auth_receive() gets called twice and executes
> > nvmet_auth_challenge(), the dhchap_c1 pointer is leaked.
>
> Thanks Maurizio.
>
> The kmemleak cannot be reproduced now after reverting that commit.
That's not the fix though, as that breaks REPLACETLSPSK.
Can you supply more logs to narrow down a fix?
Alistair
>
> >
> > Maurizio
> >
> > > unreferenced object 0xff1100027be14c00 (size 256):
> > > comm "kworker/u48:3", pid 123223, jiffies 4401374168
> > > hex dump (first 32 bytes):
> > > 30 96 ec 83 33 bb fc 41 ec 81 70 14 1e ad 32 fd
> > > 0...3..A..p...2.
> > > 39 b8 ca 9c 99 22 ff 28 f0 80 f3 e0 1d 82 36 a9
> > > 9....".(......6.
> > > backtrace (crc e365275d):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000305c48d40 (size 32):
> > > comm "kworker/u48:3", pid 123223, jiffies 4401374170
> > > hex dump (first 32 bytes):
> > > c0 8b 24 c4 c1 5a 37 d1 fc 49 ec 3e 44 05 7e 19
> > > ..$..Z7..I.>D.~.
> > > 70 39 6a d0 53 22 6d 23 fc b9 94 83 e3 3a 60 e2
> > > p9j.S"m#.....:`.
> > > backtrace (crc 8284cf12):
> > > __kmalloc_node_track_caller_noprof+0x637/0x880
> > > kmemdup_noprof+0x22/0x50
> > > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff1100016dd8c7c0 (size 32):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374600
> > > hex dump (first 32 bytes):
> > > 21 1e e5 a0 b9 e6 a0 6b 85 cb 62 ff 30 d6 21 0f
> > > !......k..b.0.!.
> > > 05 89 bc 6a 44 fe 2a c4 bd 35 23 59 6c 56 2b 2e
> > > ...jD.*..5#YlV+.
> > > backtrace (crc e32fd56c):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000255549600 (size 256):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374604
> > > hex dump (first 32 bytes):
> > > 11 1a 6e 99 d1 bc ae 48 5d aa f1 74 62 30 68 c4
> > > ..n....H]..tb0h.
> > > 07 9f 31 dc 83 a4 a4 92 47 18 9c 04 1e 7d 68 c1
> > > ..1.....G....}h.
> > > backtrace (crc db3ad817):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff1100016dd8cc00 (size 32):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374609
> > > hex dump (first 32 bytes):
> > > 51 ff e9 8e 10 6b b4 b3 3f 6c 7d f2 74 eb 42 98
> > > Q....k..?l}.t.B.
> > > 6c f8 ab ec 10 d6 e8 0f 02 79 4a e4 ec b2 ce ed
> > > l........yJ.....
> > > backtrace (crc 7099040d):
> > > __kmalloc_node_track_caller_noprof+0x637/0x880
> > > kmemdup_noprof+0x22/0x50
> > > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff1100025554a800 (size 256):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374633
> > > hex dump (first 32 bytes):
> > > eb a9 ed 0e b7 42 c6 6c 48 ee 56 29 a4 8a 99 18
> > > .....B.lH.V)....
> > > 1c 90 2a 53 22 7a ee 5a c0 6e 60 43 5b 33 a1 d2
> > > ..*S"z.Z.n`C[3..
> > > backtrace (crc 3ce24e58):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000267237a80 (size 32):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374635
> > > hex dump (first 32 bytes):
> > > 20 25 77 95 60 f2 19 5a 09 20 2c 25 8b 04 2a 4b %w.`..Z.
> > > ,%..*K
> > > b9 53 8e 10 39 b9 07 0d e0 fc 93 3f 82 50 86 0c
> > > .S..9......?.P..
> > > backtrace (crc 3f42440d):
> > > __kmalloc_node_track_caller_noprof+0x637/0x880
> > > kmemdup_noprof+0x22/0x50
> > > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000138f46e40 (size 32):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374654
> > > hex dump (first 32 bytes):
> > > 2d da 99 66 3b e7 d6 65 aa d7 1f a6 51 b4 ab 19 -
> > > ..f;..e....Q...
> > > 46 d7 30 0d 12 fd 55 90 c4 6a 4a 7a b8 55 7f 4f
> > > F.0...U..jJz.U.O
> > > backtrace (crc 3ab35d56):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000126860400 (size 256):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374658
> > > hex dump (first 32 bytes):
> > > cb 48 8c 49 58 82 bd fd 21 5b e4 a5 5b 5e 7b 8b
> > > .H.IX...![..[^{.
> > > 48 6a 47 3e 9f b7 76 06 c8 47 6a 5f 3e b4 20 15
> > > HjG>..v..Gj_>. .
> > > backtrace (crc b164cda1):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_ctrl_sesskey+0xfa/0x3a0 [nvmet]
> > > nvmet_auth_reply+0x436/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000138f468c0 (size 32):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374662
> > > hex dump (first 32 bytes):
> > > 01 dd af 3b af a0 f8 ec 61 80 c4 aa ad 56 9a 27
> > > ...;....a....V.'
> > > d4 f9 f9 8d 98 64 ce 5a 81 e2 14 e0 e3 5c 79 97
> > > .....d.Z.....\y.
> > > backtrace (crc b24f43c2):
> > > __kmalloc_node_track_caller_noprof+0x637/0x880
> > > kmemdup_noprof+0x22/0x50
> > > nvmet_auth_reply+0x2ba/0xd00 [nvmet]
> > > nvmet_execute_auth_send+0xc7f/0x14f0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> > > unreferenced object 0xff11000185c80580 (size 64):
> > > comm "kworker/u48:2", pid 139664, jiffies 4401374716
> > > hex dump (first 32 bytes):
> > > bf a4 73 5a 5c a7 d7 8e f7 6e f9 39 3a 94 66 a4
> > > ..sZ\....n.9:.f.
> > > 8e f9 bc f6 9a 23 ac dc c8 71 85 ef 09 4c ac 38
> > > .....#...q...L.8
> > > backtrace (crc 70f5e8bf):
> > > __kmalloc_noprof+0x635/0x870
> > > nvmet_auth_challenge+0x329/0x9f0 [nvmet]
> > > nvmet_execute_auth_receive+0x381/0x7b0 [nvmet]
> > > process_one_work+0xd98/0x1390
> > > worker_thread+0x60b/0x1000
> > > kthread+0x36c/0x470
> > > ret_from_fork+0x5dc/0x8e0
> > > ret_from_fork_asm+0x1a/0x30
> >
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-04-07 1:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-03 8:46 [bug report]nvmet_auth kmemleak observed during blktests Yi Zhang
2026-04-03 9:21 ` Maurizio Lombardi
2026-04-07 0:54 ` Yi Zhang
2026-04-07 1:23 ` Alistair Francis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox