From: Leon Romanovsky <leonro@nvidia.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: RDMA mailing list <linux-rdma@vger.kernel.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [bug report] kmemleak in rdma_core observed during blktests nvme/rdma use siw
Date: Mon, 8 Apr 2024 09:57:10 +0300 [thread overview]
Message-ID: <20240408065710.GC8764@unreal> (raw)
In-Reply-To: <20240408063907.GB8764@unreal>
On Mon, Apr 08, 2024 at 09:39:07AM +0300, Leon Romanovsky wrote:
> On Mon, Apr 08, 2024 at 02:03:51PM +0800, Yi Zhang wrote:
> > Hi
> > I found the below kmemleak issue during blktests nvme/rdma on the
> > latest linux-rdma/for-next, please help check it and let me know if
> > you need any info/testing for it, thanks.
> >
> > # dmesg | grep kmemleak
> > [ 67.130652] kmemleak: Kernel memory leak detector initialized (mem
> > pool available: 36041)
> > [ 67.130728] kmemleak: Automatic memory scanning thread started
> > [ 1051.771867] kmemleak: 2 new suspected memory leaks (see
> > /sys/kernel/debug/kmemleak)
> > [ 1832.796189] kmemleak: 8 new suspected memory leaks (see
> > /sys/kernel/debug/kmemleak)
> > [ 2578.189075] kmemleak: 17 new suspected memory leaks (see
> > /sys/kernel/debug/kmemleak)
> > [ 3330.710984] kmemleak: 4 new suspected memory leaks (see
> > /sys/kernel/debug/kmemleak)
> >
> > unreferenced object 0xffff88855da53400 (size 192):
> > comm "rdma", pid 10630, jiffies 4296575922
> > hex dump (first 32 bytes):
> > 37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00 7...............
> > 10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff .4.].....4.]....
> > backtrace (crc 47f66721):
> > [<ffffffff911251bd>] kmalloc_trace+0x30d/0x3b0
> > [<ffffffffc2640ff7>] alloc_gid_entry+0x47/0x380 [ib_core]
> > [<ffffffffc2642206>] add_modify_gid+0x166/0x930 [ib_core]
> > [<ffffffffc2643468>] ib_cache_update.part.0+0x6d8/0x910 [ib_core]
> > [<ffffffffc2644e1a>] ib_cache_setup_one+0x24a/0x350 [ib_core]
> > [<ffffffffc263949e>] ib_register_device+0x9e/0x3a0 [ib_core]
> > [<ffffffffc2a3d389>] 0xffffffffc2a3d389
> > [<ffffffffc2688cd8>] nldev_newlink+0x2b8/0x520 [ib_core]
>
> My guess is that your test didn't call too nldev_dellink() and left
> device registered.
Sorry, I was wrong, it looks like GID entry leak.
Thanks
>
> Thanks
>
> > [<ffffffffc2645fe3>] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]
> > [<ffffffffc264648c>]
> > rdma_nl_rcv_skb.constprop.0.isra.0+0x23c/0x3a0 [ib_core]
> > [<ffffffff9270e7b5>] netlink_unicast+0x445/0x710
> > [<ffffffff9270f1f1>] netlink_sendmsg+0x761/0xc40
> > [<ffffffff9249db29>] __sys_sendto+0x3a9/0x420
> > [<ffffffff9249dc8c>] __x64_sys_sendto+0xdc/0x1b0
> > [<ffffffff92db0ad3>] do_syscall_64+0x93/0x180
> > [<ffffffff92e00126>] entry_SYSCALL_64_after_hwframe+0x71/0x79
> >
> > --
> > Best Regards,
> > Yi Zhang
> >
> >
>
next prev parent reply other threads:[~2024-04-08 6:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 6:03 [bug report] kmemleak in rdma_core observed during blktests nvme/rdma use siw Yi Zhang
2024-04-08 6:39 ` Leon Romanovsky
2024-04-08 6:57 ` Leon Romanovsky [this message]
2024-04-24 13:28 ` Guoqing Jiang
2024-04-26 5:56 ` Yi Zhang
2024-04-26 8:44 ` Yi Zhang
2024-04-28 2:54 ` Guoqing Jiang
2024-04-28 12:42 ` Yi Zhang
2024-04-29 0:53 ` Guoqing Jiang
2024-04-30 11:51 ` Yi Zhang
2024-05-08 13:08 ` [bug report][bisected] " Yi Zhang
2024-05-08 14:37 ` Zhu Yanjun
2024-05-08 15:31 ` Zhu Yanjun
2024-05-08 15:56 ` Jason Gunthorpe
2024-05-08 16:19 ` Chuck Lever
2024-05-10 1:41 ` Yi Zhang
2024-05-10 11:10 ` Zhu Yanjun
[not found] ` <a6b11edf-99e0-43bc-b49e-e0d6e201266b@linux.dev>
[not found] ` <CAHj4cs9XsHiKeVGNRjTCcg87ghWrDm972VMq+5w=8jvetjFG0w@mail.gmail.com>
2024-05-10 15:52 ` Zhu Yanjun
2024-04-24 15:57 ` [bug report] " Zhu Yanjun
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=20240408065710.GC8764@unreal \
--to=leonro@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yi.zhang@redhat.com \
/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 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).