From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with ESMTP id B27118D0040 for ; Wed, 30 Mar 2011 09:27:13 -0400 (EDT) Received: by fxm18 with SMTP id 18so1419568fxm.14 for ; Wed, 30 Mar 2011 06:27:06 -0700 (PDT) Subject: Re: kmemleak for MIPS From: Eric Dumazet In-Reply-To: References: <9bde694e1003020554p7c8ff3c2o4ae7cb5d501d1ab9@mail.gmail.com> <1300960540.32158.13.camel@e102109-lin.cambridge.arm.com> <1301395206.583.53.camel@e102109-lin.cambridge.arm.com> <1301399454.583.66.camel@e102109-lin.cambridge.arm.com> <1301476505.29074.47.camel@e102109-lin.cambridge.arm.com> <1301485085.29074.61.camel@e102109-lin.cambridge.arm.com> <1301488032.3283.42.camel@edumazet-laptop> Content-Type: text/plain; charset="UTF-8" Date: Wed, 30 Mar 2011 15:27:02 +0200 Message-ID: <1301491622.3283.46.camel@edumazet-laptop> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Maxin John Cc: Daniel Baluta , Catalin Marinas , naveen yadav , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Le mercredi 30 mars 2011 A 14:17 +0100, Maxin John a A(C)crit : > Hi, > > I have compiled the kernel with below given modification in .config > > CONFIG_CMDLINE="uhash_entries=256" > > After booting with the new kernel, the "kmemleak" no longer complains > about the "udp_table_init". > However it do report another possible leak :) > > debian-mips:~# cat /sys/kernel/debug/kmemleak > unreferenced object 0x8f085000 (size 4096): > comm "swapper", pid 1, jiffies 4294937670 (age 1043.280s) > hex dump (first 32 bytes): > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > backtrace: > [<801ac7a8>] __kmalloc+0x130/0x180 > [<80532500>] flow_cache_cpu_prepare+0x50/0xa8 > [<8052378c>] flow_cache_init_global+0x90/0x138 > [<80100584>] do_one_initcall+0x174/0x1e0 > [<8050c348>] kernel_init+0xe4/0x174 > [<80103d4c>] kernel_thread_helper+0x10/0x18 > debian-mips:~# Hmm, then MIPS kmemleak port might have a problem with percpu data ? fcp->hash_table = kzalloc_node(sz, GFP_KERNEL, cpu_to_node(cpu)); fcp is a per cpu "struct flow_cache_percpu" > I completely agree with Daniel. Shall we move on and integrate the > kmemleak support for MIPS ? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org