From: Victor Gladkov <Victor.Gladkov@kioxia.com>
To: Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: RE: [bug report] nvmet-tcp: Memory leak when connecting / disconnecting to the target
Date: Tue, 2 Jun 2020 09:14:46 +0000 [thread overview]
Message-ID: <137723703f2c489e87005cf018ddc0a6@kioxia.com> (raw)
In-Reply-To: <29ca9be1-22d3-dba6-b2d1-648b27e471cc@grimberg.me>
> > [Environment]
> > Branch: nvme-5.7
> > Commit: 9210c075cef29c1f764b4252f93105103bdfb292
>
> Hi, can you please provide kmemleak output for this test case?
>
> Is this specific to nvmet-tcp? what about nvmet-rdma?
Kmemleak doesn't report any leaks :(
It's happening with nvmet-tcp only. The nvmet-rdma works without leaks.
Target terminal record
----
# lsmod|grep kmem
kmemleak_test 16384 0
#
# modinfo kmemleak_test
filename: /lib/modules/5.7.0-rc1+KS+/kernel/mm/kmemleak-test.ko
license: GPL
srcversion: 67EF7E2143EBE69D39BFA1A
depends:
retpoline: Y
intree: Y
name: kmemleak_test
vermagic: 5.7.0-rc1+KS+ SMP mod_unload modversions
#
#
# ./target_load_drivers.sh
nvmet_tcp 28672 0
nvmet_rdma 36864 0
nvmet 102400 2 nvmet_tcp,nvmet_rdma
rdma_cm 118784 7 rpcrdma,ib_srpt,ib_srp,nvmet_rdma,ib_iser,ib_isert,rdma_ucm
ib_core 409600 14 rdma_cm,ib_ipoib,rpcrdma,ib_srpt,ib_srp,nvmet_rdma,iw_cm,ib_iser,ib_umad,ib_isert,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
nvme 49152 4
nvme_core 110592 6 nvme
t10_pi 16384 2 sd_mod,nvme_core
#
# ./target_create_portal.sh 1 69.69.69.1 4420 tcp
transport type is tcp
/sys/kernel/config/nvmet/ports/1
#
# ./target_add.sh /dev/nvme1n1 target_t0 1
#
# dmesg -c
#
# date
Tue Jun 2 05:01:09 EDT 2020
#
# grep Free /proc/meminfo
MemFree: 61740020 kB
SwapFree: 32964604 kB
HugePages_Free: 0
#
# cat /sys/kernel/debug/kmemleak
#
# echo scan > /sys/kernel/debug/kmemleak
# cat /sys/kernel/debug/kmemleak
#
# date
Tue Jun 2 05:04:12 EDT 2020
#
# dmesg |grep -c "creating controller 1 for subsystem target_t0 for"
1001
#
# grep Free /proc/meminfo
MemFree: 61370724 kB
SwapFree: 32964604 kB
HugePages_Free: 0
#
# echo scan > /sys/kernel/debug/kmemleak
# cat /sys/kernel/debug/kmemleak
#
-------
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-06-02 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 15:28 [bug report] nvmet-tcp: Memory leak when connecting / disconnecting to the target Victor Gladkov
2020-06-02 7:26 ` Sagi Grimberg
2020-06-02 9:14 ` Victor Gladkov [this message]
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=137723703f2c489e87005cf018ddc0a6@kioxia.com \
--to=victor.gladkov@kioxia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox