public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Michal Kalderon <Michal.Kalderon@cavium.com>,
	linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: qedr memory leak report
Date: Sat, 31 Aug 2019 10:33:13 -0400	[thread overview]
Message-ID: <63286035eb752429fdb651750acf74765caecfe5.camel@redhat.com> (raw)
In-Reply-To: <20190831073048.GH12611@unreal>

[-- Attachment #1: Type: text/plain, Size: 3591 bytes --]

On Sat, 2019-08-31 at 10:30 +0300, Leon Romanovsky wrote:
> Doug,
> 
> I think that it can be counted as good example why allowing memory
> leaks
> in drivers (HNS) is not so great idea.

Crashing the machine is worse.

> Thanks
> 
> On Fri, Aug 30, 2019 at 02:27:49PM -0400, Chuck Lever wrote:
> > > On Aug 30, 2019, at 2:03 PM, Chuck Lever <chuck.lever@oracle.com>
> > > wrote:
> > > 
> > > Hi Michal-
> > > 
> > > In the middle of some other testing, I got this kmemleak report
> > > while testing with FastLinq cards in iWARP mode:
> > > 
> > > unreferenced object 0xffff888458923340 (size 32):
> > >  comm "mount.nfs", pid 2294, jiffies 4298338848 (age 1144.337s)
> > >  hex dump (first 32 bytes):
> > >    20 1d 69 63 88 88 ff ff 20 1d 69 63 88 88 ff ff   .ic....
> > > .ic....
> > >    00 60 7a 69 84 88 ff ff 00 60 82 f9 00 00 00
> > > 00  .`zi.....`......
> > >  backtrace:
> > >    [<000000000df5bfed>] __kmalloc+0x128/0x176
> > >    [<0000000020724641>] qedr_alloc_pbl_tbl.constprop.44+0x3c/0x121
> > > [qedr]
> > >    [<00000000a361c591>] init_mr_info.constprop.41+0xaf/0x21f
> > > [qedr]
> > >    [<00000000e8049714>] qedr_alloc_mr+0x95/0x2c1 [qedr]
> > >    [<000000000e6102bc>] ib_alloc_mr_user+0x31/0x96 [ib_core]
> > >    [<00000000d254a9fb>] frwr_init_mr+0x23/0x121 [rpcrdma]
> > >    [<00000000a0364e35>] rpcrdma_mrs_create+0x45/0xea [rpcrdma]
> > >    [<00000000fd6bf282>] rpcrdma_buffer_create+0x9e/0x1c9 [rpcrdma]
> > >    [<00000000be3a1eba>] xprt_setup_rdma+0x109/0x279 [rpcrdma]
> > >    [<00000000b736b88f>] xprt_create_transport+0x39/0x19a [sunrpc]
> > >    [<000000001024e4dc>] rpc_create+0x118/0x1ab [sunrpc]
> > >    [<00000000cca43a49>] nfs_create_rpc_client+0xf8/0x15f [nfs]
> > >    [<00000000073c962c>] nfs_init_client+0x1a/0x3b [nfs]
> > >    [<00000000b03964c4>] nfs_init_server+0xc1/0x212 [nfs]
> > >    [<000000001c71f609>] nfs_create_server+0x74/0x1a4 [nfs]
> > >    [<000000004dc919a1>] nfs3_create_server+0xb/0x25 [nfsv3]
> > > 
> > > It's repeated many times.
> > > 
> > > The workload was an unremarkable software build and regression
> > > test
> > > suite on an NFSv3 mount with RDMA.
> > 
> > Also seeing one of these per NFS mount:
> > 
> > unreferenced object 0xffff888869f39b40 (size 64):
> >   comm "kworker/u28:0", pid 17569, jiffies 4299267916 (age
> > 1592.907s)
> >   hex dump (first 32 bytes):
> >     00 80 53 6d 88 88 ff ff 00 00 00 00 00 00 00
> > 00  ..Sm............
> >     00 48 e2 66 84 88 ff ff 00 00 00 00 00 00 00
> > 00  .H.f............
> >   backtrace:
> >     [<0000000063e652dd>] kmem_cache_alloc_trace+0xed/0x133
> >     [<0000000083b1e912>] qedr_iw_connect+0xf9/0x3c8 [qedr]
> >     [<00000000553be951>] iw_cm_connect+0xd0/0x157 [iw_cm]
> >     [<00000000b086730c>] rdma_connect+0x54e/0x5b0 [rdma_cm]
> >     [<00000000d8af3cf2>] rpcrdma_ep_connect+0x22b/0x360 [rpcrdma]
> >     [<000000006a413c8d>] xprt_rdma_connect_worker+0x24/0x88
> > [rpcrdma]
> >     [<000000001c5b049a>] process_one_work+0x196/0x2c6
> >     [<000000007e3403ba>] worker_thread+0x1ad/0x261
> >     [<000000001daaa973>] kthread+0xf4/0xf9
> >     [<0000000014987b31>] ret_from_fork+0x24/0x30
> > 
> > Looks like this one is not being freed:
> > 
> > 514         ep = kzalloc(sizeof(*ep), GFP_KERNEL);
> > 515         if (!ep)
> > 516                 return -ENOMEM;
> > 
> > 
> > --
> > Chuck Lever
> > 
> > 
> > 

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-08-31 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 18:03 qedr memory leak report Chuck Lever
2019-08-30 18:27 ` Chuck Lever
2019-08-31  7:30   ` Leon Romanovsky
2019-08-31 14:33     ` Doug Ledford [this message]
2019-08-31 15:19       ` Leon Romanovsky
2019-08-31 17:17         ` Doug Ledford
2019-08-31 18:55           ` Leon Romanovsky
2019-09-02  7:53   ` [EXT] " Michal Kalderon
2019-09-03 12:53     ` Chuck Lever

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=63286035eb752429fdb651750acf74765caecfe5.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=Michal.Kalderon@cavium.com \
    --cc=chuck.lever@oracle.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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