All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Zhang <yi.zhang@redhat.com>
To: linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, Sagi Grimberg <sagi@grimberg.me>
Subject: [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect
Date: Wed, 4 Mar 2020 10:08:07 -0500 (EST)	[thread overview]
Message-ID: <215235485.15264050.1583334487658.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <716376633.15258107.1583333480546.JavaMail.zimbra@redhat.com>

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

       reply	other threads:[~2020-03-04 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <716376633.15258107.1583333480546.JavaMail.zimbra@redhat.com>
2020-03-04 15:08 ` Yi Zhang [this message]
2020-03-05 20:57   ` [bug report] NVMe RDMA OPA: kmemleak observed with connect/reset_controller/disconnect Sagi Grimberg
2020-03-05 20:57     ` Sagi Grimberg
2020-03-06 15:03     ` Dennis Dalessandro
2020-03-06 15:03       ` Dennis Dalessandro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=215235485.15264050.1583334487658.JavaMail.zimbra@redhat.com \
    --to=yi.zhang@redhat.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.