linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect
       [not found] <716376633.15258107.1583333480546.JavaMail.zimbra@redhat.com>
@ 2020-03-04 15:08 ` Yi Zhang
  2020-03-05 20:57   ` Sagi Grimberg
  0 siblings, 1 reply; 3+ messages in thread
From: Yi Zhang @ 2020-03-04 15:08 UTC (permalink / raw)
  To: linux-nvme; +Cc: kbusch, Sagi Grimberg

Hello

I would like to report a kmemleak issue found on NVMe RDMA OPA environment, here is the log, let me know if you need more info

unreferenced object 0xffffc90006639000 (size 12288):
  comm "kworker/u128:0", pid 8, jiffies 4295777598 (age 589.085s)
  hex dump (first 32 bytes):
    4d 00 00 00 4d 00 00 00 00 c0 08 ac 8b 88 ff ff  M...M...........
    00 00 00 00 80 00 00 00 00 00 00 00 10 00 00 00  ................
  backtrace:
    [<0000000035a3d625>] __vmalloc_node_range+0x361/0x720
    [<000000002942ce4f>] __vmalloc_node.constprop.30+0x63/0xb0
    [<00000000f228f784>] rvt_create_cq+0x98a/0xd80 [rdmavt]
    [<00000000b84aec66>] __ib_alloc_cq_user+0x281/0x1260 [ib_core]
    [<00000000ef3764be>] nvme_rdma_cm_handler+0xdb7/0x1b80 [nvme_rdma]
    [<00000000936b401c>] cma_cm_event_handler+0xb7/0x550 [rdma_cm]
    [<00000000d9c40b7b>] addr_handler+0x195/0x310 [rdma_cm]
    [<00000000c7398a03>] process_one_req+0xdd/0x600 [ib_core]
    [<000000004d29675b>] process_one_work+0x920/0x1740
    [<00000000efedcdb5>] worker_thread+0x87/0xb40
    [<000000005688b340>] kthread+0x327/0x3f0
    [<0000000043a168d6>] ret_from_fork+0x3a/0x50
unreferenced object 0xffffc90008581000 (size 36864):
  comm "kworker/u128:0", pid 8, jiffies 4295778075 (age 588.608s)
  hex dump (first 32 bytes):
    84 00 00 00 84 00 00 00 40 01 36 5d 84 88 ff ff  ........@.6]....
    00 00 00 00 00 00 00 00 00 00 00 00 40 04 00 00  ............@...
  backtrace:
    [<0000000035a3d625>] __vmalloc_node_range+0x361/0x720
    [<000000002942ce4f>] __vmalloc_node.constprop.30+0x63/0xb0
    [<00000000f228f784>] rvt_create_cq+0x98a/0xd80 [rdmavt]
    [<00000000b84aec66>] __ib_alloc_cq_user+0x281/0x1260 [ib_core]
    [<00000000ef3764be>] nvme_rdma_cm_handler+0xdb7/0x1b80 [nvme_rdma]
    [<00000000936b401c>] cma_cm_event_handler+0xb7/0x550 [rdma_cm]
    [<00000000d9c40b7b>] addr_handler+0x195/0x310 [rdma_cm]
    [<00000000c7398a03>] process_one_req+0xdd/0x600 [ib_core]
    [<000000004d29675b>] process_one_work+0x920/0x1740
    [<00000000efedcdb5>] worker_thread+0x87/0xb40
    [<000000005688b340>] kthread+0x327/0x3f0
    [<0000000043a168d6>] ret_from_fork+0x3a/0x50


Best Regards,
  Yi Zhang



_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect
  2020-03-04 15:08 ` [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect Yi Zhang
@ 2020-03-05 20:57   ` Sagi Grimberg
  2020-03-06 15:03     ` Dennis Dalessandro
  0 siblings, 1 reply; 3+ messages in thread
From: Sagi Grimberg @ 2020-03-05 20:57 UTC (permalink / raw)
  To: Yi Zhang, linux-nvme; +Cc: kbusch, linux-rdma

CCing Linux-rdma as I don't think anyone in nvme will
have a clue to whats going on here...

On 3/4/20 7:08 AM, Yi Zhang wrote:
> Hello
> 
> I would like to report a kmemleak issue found on NVMe RDMA OPA environment, here is the log, let me know if you need more info
> 
> unreferenced object 0xffffc90006639000 (size 12288):
>    comm "kworker/u128:0", pid 8, jiffies 4295777598 (age 589.085s)
>    hex dump (first 32 bytes):
>      4d 00 00 00 4d 00 00 00 00 c0 08 ac 8b 88 ff ff  M...M...........
>      00 00 00 00 80 00 00 00 00 00 00 00 10 00 00 00  ................
>    backtrace:
>      [<0000000035a3d625>] __vmalloc_node_range+0x361/0x720
>      [<000000002942ce4f>] __vmalloc_node.constprop.30+0x63/0xb0
>      [<00000000f228f784>] rvt_create_cq+0x98a/0xd80 [rdmavt]
>      [<00000000b84aec66>] __ib_alloc_cq_user+0x281/0x1260 [ib_core]
>      [<00000000ef3764be>] nvme_rdma_cm_handler+0xdb7/0x1b80 [nvme_rdma]
>      [<00000000936b401c>] cma_cm_event_handler+0xb7/0x550 [rdma_cm]
>      [<00000000d9c40b7b>] addr_handler+0x195/0x310 [rdma_cm]
>      [<00000000c7398a03>] process_one_req+0xdd/0x600 [ib_core]
>      [<000000004d29675b>] process_one_work+0x920/0x1740
>      [<00000000efedcdb5>] worker_thread+0x87/0xb40
>      [<000000005688b340>] kthread+0x327/0x3f0
>      [<0000000043a168d6>] ret_from_fork+0x3a/0x50
> unreferenced object 0xffffc90008581000 (size 36864):
>    comm "kworker/u128:0", pid 8, jiffies 4295778075 (age 588.608s)
>    hex dump (first 32 bytes):
>      84 00 00 00 84 00 00 00 40 01 36 5d 84 88 ff ff  ........@.6]....
>      00 00 00 00 00 00 00 00 00 00 00 00 40 04 00 00  ............@...
>    backtrace:
>      [<0000000035a3d625>] __vmalloc_node_range+0x361/0x720
>      [<000000002942ce4f>] __vmalloc_node.constprop.30+0x63/0xb0
>      [<00000000f228f784>] rvt_create_cq+0x98a/0xd80 [rdmavt]
>      [<00000000b84aec66>] __ib_alloc_cq_user+0x281/0x1260 [ib_core]
>      [<00000000ef3764be>] nvme_rdma_cm_handler+0xdb7/0x1b80 [nvme_rdma]
>      [<00000000936b401c>] cma_cm_event_handler+0xb7/0x550 [rdma_cm]
>      [<00000000d9c40b7b>] addr_handler+0x195/0x310 [rdma_cm]
>      [<00000000c7398a03>] process_one_req+0xdd/0x600 [ib_core]
>      [<000000004d29675b>] process_one_work+0x920/0x1740
>      [<00000000efedcdb5>] worker_thread+0x87/0xb40
>      [<000000005688b340>] kthread+0x327/0x3f0
>      [<0000000043a168d6>] ret_from_fork+0x3a/0x50
> 
> 
> Best Regards,
>    Yi Zhang
> 
> 

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect
  2020-03-05 20:57   ` Sagi Grimberg
@ 2020-03-06 15:03     ` Dennis Dalessandro
  0 siblings, 0 replies; 3+ messages in thread
From: Dennis Dalessandro @ 2020-03-06 15:03 UTC (permalink / raw)
  To: Sagi Grimberg, Yi Zhang, linux-nvme; +Cc: kbusch, linux-rdma

On 3/5/2020 3:57 PM, Sagi Grimberg wrote:
> CCing Linux-rdma as I don't think anyone in nvme will
> have a clue to whats going on here...
> 

We will take a look at it. Thanks for forwarding!

-Denny


_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-03-06 15:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <716376633.15258107.1583333480546.JavaMail.zimbra@redhat.com>
2020-03-04 15:08 ` [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect Yi Zhang
2020-03-05 20:57   ` Sagi Grimberg
2020-03-06 15:03     ` Dennis Dalessandro

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).