From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752240Ab1I0RFc (ORCPT ); Tue, 27 Sep 2011 13:05:32 -0400 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:33487 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751713Ab1I0RFb (ORCPT ); Tue, 27 Sep 2011 13:05:31 -0400 Date: Tue, 27 Sep 2011 18:01:34 +0100 From: Catalin Marinas To: Eric Dumazet Cc: Huajun Li , "linux-mm@kvack.org" , netdev , linux-kernel , Tejun Heo , Christoph Lameter Subject: Re: Question about memory leak detector giving false positive report for net/core/flow.c Message-ID: <20110927170133.GN14237@e102109-lin.cambridge.arm.com> References: <1317054774.6363.9.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20110926165024.GA21617@e102109-lin.cambridge.arm.com> <1317066395.2796.11.camel@edumazet-laptop> <1317102918.2796.22.camel@edumazet-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1317102918.2796.22.camel@edumazet-laptop> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 27, 2011 at 06:55:18AM +0100, Eric Dumazet wrote: > Yes, it was not a patch, but the general idea for Catalin ;) > > You hit the fact that same zone (embedded percpu space) is now in a > mixed state. > > In current kernels, the embedded percpu zone is already known by > kmemleak, but with a large granularity. kmemleak is not aware of > individual allocations/freeing in this large zone. It looks like this comes via the bootmem allocator. Maybe we could simply call kmemleak_free() on the embedded percpu space and just track those via the standard percpu API. -- Catalin