[PATCHv17 00/11] nvme: In-band authentication support

[Sagi Grimberg]

>>> 3. Not sure if this is related, but now I see a new memory leak:
>>> -- 
>>> unreferenced object 0xffff8fa0c91d2080 (size 128):
>>>    comm "kworker/u8:4", pid 262, jiffies 4294949965 (age 1855.437s)
>>>    hex dump (first 32 bytes):
>>>      e0 a2 c9 96 ff ff ff ff 90 0f dd f4 a0 8f ff ff  ................
>>>      01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>>>    backtrace:
>>>      [<000000009524c6a1>] blk_iolatency_init+0x25/0x160
>>>      [<0000000074c7283e>] blkcg_init_queue+0xb4/0x120
>>>      [<00000000747d5b28>] __alloc_disk_node+0xeb/0x1d0
>>>      [<0000000082cf1eb2>] __blk_alloc_disk+0x31/0x60
>>>      [<000000008e36f1d8>] nvme_mpath_alloc_disk+0xcc/0x1c0 [nvme_core]
>>>      [<00000000f81c9db1>] nvme_alloc_ns_head+0x12b/0x250 [nvme_core]
>>>      [<00000000eba12e37>] nvme_init_ns_head+0x255/0x2d0 [nvme_core]
>>>      [<000000006f769fbb>] nvme_alloc_ns+0x114/0x4b0 [nvme_core]
>>>      [<00000000cf38f67b>] nvme_validate_or_alloc_ns+0x9e/0x1c0 
>>> [nvme_core]
>>>      [<00000000db73ed81>] nvme_scan_ns_list+0xf7/0x2c0 [nvme_core]
>>>      [<0000000011b21727>] nvme_scan_work+0xde/0x270 [nvme_core]
>>>      [<000000000f7941ae>] process_one_work+0x1e5/0x3b0
>>>      [<000000008eb36ec1>] worker_thread+0x50/0x3a0
>>>      [<00000000e58a93ca>] kthread+0xe8/0x110
>>>      [<00000000e82e51e5>] ret_from_fork+0x22/0x30
>>> -- 
>>
>> Hmm. Looks like a generic nvme issue, so unlikely it's introduced by 
>> this patch. We still should fix it, though :-)
> 
> I'll have a look.

CC'ing Ming, this came back since commit:

285d5731a0cb ("Revert "block: release rq qos structures for queue 
without disk"")