Re: [PATCH 1/1] bridge: mdb: report complete_info ptr as not a kmemleak

2017-07-11 Thread Eduardo Valentin
On Wed, Jul 05, 2017 at 09:05:14AM -0700, Eduardo Valentin wrote: > On Tue, Jul 04, 2017 at 01:48:42AM -0700, David Miller wrote: > > From: Eduardo Valentin > > Date: Mon, 3 Jul 2017 10:06:34 -0700 > > > > > We currently get the following kmemleak report: > > ... > > > This patch flags the compl

Re: [PATCH 1/1] bridge: mdb: report complete_info ptr as not a kmemleak

2017-07-05 Thread Eduardo Valentin
On Tue, Jul 04, 2017 at 01:48:42AM -0700, David Miller wrote: > From: Eduardo Valentin > Date: Mon, 3 Jul 2017 10:06:34 -0700 > > > We currently get the following kmemleak report: > ... > > This patch flags the complete_info ptr object as not a leak as it will > > get freed when .complete_priv()

Re: [PATCH 1/1] bridge: mdb: report complete_info ptr as not a kmemleak

2017-07-04 Thread David Miller
From: Eduardo Valentin Date: Mon, 3 Jul 2017 10:06:34 -0700 > We currently get the following kmemleak report: ... > This patch flags the complete_info ptr object as not a leak as it will > get freed when .complete_priv() is called, We don't call .complete_priv(). We call .complete(). for the

[PATCH 1/1] bridge: mdb: report complete_info ptr as not a kmemleak

2017-07-03 Thread Eduardo Valentin
We currently get the following kmemleak report: unreferenced object 0x8800039d9820 (size 32): comm "softirq", pid 0, jiffies 4295212383 (age 792.416s) hex dump (first 32 bytes): 00 0c e0 03 00 88 ff ff ff 02 00 00 00 00 00 00 00 00 00 01 ff 11 00 02 86 dd 00 00 ff