From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752551AbdBIBit (ORCPT ); Wed, 8 Feb 2017 20:38:49 -0500 Received: from mx2.suse.de ([195.135.220.15]:57189 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941AbdBIBih (ORCPT ); Wed, 8 Feb 2017 20:38:37 -0500 Date: Thu, 9 Feb 2017 02:37:32 +0100 From: "Luis R. Rodriguez" To: Michal Hocko Cc: "Luis R. Rodriguez" , Andrew Morton , Ingo Molnar , Andy Lutomirski , Kees Cook , "Eric W. Biederman" , Mateusz Guzik , "linux-kernel@vger.kernel.org" Subject: Re: kmemleak splat on copy_process() Message-ID: <20170209013732.GL24047@wotan.suse.de> References: <20170206094741.GB3097@dhcp22.suse.cz> <20170207013702.GF24047@wotan.suse.de> <20170207080343.GA5065@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170207080343.GA5065@dhcp22.suse.cz> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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