Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932540Ab1C3OHM (ORCPT ); Wed, 30 Mar 2011 10:07:12 -0400 Received: from mail-qy0-f181.google.com ([209.85.216.181]:33238 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754746Ab1C3OHK (ORCPT ); Wed, 30 Mar 2011 10:07:10 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dLLWp91hc0DC0EDB1Pu9fuSyGBYJJAf/K4885nyeAstfbvLpo7h2kSmBqiYXBIAUP9 xiuxAEJW+hjyd8STo1EezxuzamWdLv1H5I1vt8jDM2QBIenFU6gthTyDiUIin3bp56u5 QDTGgP+K3N/5cTfdip7LAL74LIaiKogJmcfho= MIME-Version: 1.0 In-Reply-To: <1301491622.3283.46.camel@edumazet-laptop> 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> <1301491622.3283.46.camel@edumazet-laptop> Date: Wed, 30 Mar 2011 15:07:09 +0100 Message-ID: Subject: Re: kmemleak for MIPS From: Maxin John To: Eric Dumazet Cc: Daniel Baluta , Catalin Marinas , naveen yadav , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 830 Lines: 25 Hi Eric, > 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" Thank you very much for the inputs. I will definitely investigate this. However, I think, the "basic" kmemleak support for MIPS is working as expected with the present patch. The kmemleak test case is also working as expected in MIPS target. So, as Daniel mentioned, shall we go ahead with integrating the kmemleak support for MIPS ? Please let me know your comments. Cheers, Maxin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/