On Wed, Nov 02, 2016 at 11:47:55PM +, Jakub Kicinski wrote:
> I realized that kmemleak is not scanning the __ro_after_init section...
> Following patch solves the false positives but I wonder if it's the
> right/acceptable solution.
Thanks for putting this together. I actually hit a similar
Hi,
Sorry for not chipping in earlier - LPC is taking my time.
> > > > Looks like we are missing a kfree(family->attrbuf); on error
> > > > path, but it is not related to Johannes' recent patches.
Actually, I think it *is* related to my patch - I inserted the code
there in the wrong place or
On Wed, Nov 2, 2016 at 4:47 PM, Jakub Kicinski wrote:
>
> Thanks for looking into this! Bisect led me to the following commit:
>
> commit 56989f6d8568c21257dcec0f5e644d5570ba3281
> Author: Johannes Berg
> Date: Mon Oct 24 14:40:05 2016 +0200
>
>
On Wed, 2 Nov 2016 13:30:34 -0700, Cong Wang wrote:
> On Tue, Nov 1, 2016 at 11:56 AM, Jakub Kicinski wrote:
> > On Tue, 1 Nov 2016 11:32:52 -0700, Cong Wang wrote:
> >> On Tue, Nov 1, 2016 at 10:28 AM, Jakub Kicinski wrote:
> >> > unreferenced object