[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170209013732.GL24047@wotan.suse.de>
Date: Thu, 9 Feb 2017 02:37:32 +0100
From: "Luis R. Rodriguez" <mcgrof@...nel.org>
To: Michal Hocko <mhocko@...nel.org>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>,
Andy Lutomirski <luto@...nel.org>,
Kees Cook <keescook@...omium.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Mateusz Guzik <mguzik@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: kmemleak splat on copy_process()
On Tue, Feb 07, 2017 at 09:03:43AM +0100, Michal Hocko wrote:
> On Tue 07-02-17 02:37:02, Luis R. Rodriguez wrote:
> > > From a quick check I do not see any leak there either.
> >
> > Then in that case what about:
>
> This just disables the kmemleak altogether which doesn't sound like a
> good idea to me.
Only for this case, but if that is also not desirable let us debug further.
That or I think we could perhaps massage code to make it clearer to kmemleak
things are good.
Luis
Powered by blists - more mailing lists