Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759648Ab3EOQxU (ORCPT ); Wed, 15 May 2013 12:53:20 -0400 Received: from fw-tnat.cambridge.arm.com ([217.140.96.21]:48452 "EHLO cam-smtp0.cambridge.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758319Ab3EOQxR (ORCPT ); Wed, 15 May 2013 12:53:17 -0400 Date: Wed, 15 May 2013 17:47:43 +0100 From: Catalin Marinas To: Toshi Kani Cc: "rjw@sisk.pl" , Larry Finger , Steven Rostedt , "zhangwei(Jovi)" , Masami Hiramatsu , LKML , Rusty Russell , "linux-acpi@vger.kernel.org" Subject: Re: V3.10-rc1 memory leak Message-ID: <20130515164743.GD9324@arm.com> References: <51912567.6090507@lwfinger.net> <1368558586.6828.53.camel@gandalf.local.home> <20130514203028.GA2997@MacBook-Pro.local> <5192A847.1000100@lwfinger.net> <1368566427.6828.58.camel@gandalf.local.home> <1368579423.6828.63.camel@gandalf.local.home> <5192FDE2.1020305@lwfinger.net> <20130515150228.GC1096@darko.cambridge.arm.com> <1368632990.5673.33.camel@misato.fc.hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1368632990.5673.33.camel@misato.fc.hp.com> 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 Content-Length: 2914 Lines: 61 On Wed, May 15, 2013 at 04:49:50PM +0100, Toshi Kani wrote: > On Wed, 2013-05-15 at 16:02 +0100, Catalin Marinas wrote: > > On Wed, May 15, 2013 at 04:15:46AM +0100, Larry Finger wrote: > > > I do not see that particular one; however, I see 4 instances of > > > > > > unreferenced object 0xffff8800b7979750 (size 8): > > > comm "swapper/0", pid 1, jiffies 4294892402 (age 21888.316s) > > > hex dump (first 8 bytes): > > > 31 38 00 b7 00 88 ff ff 18...... > > > backtrace: > > > [] kmemleak_alloc+0x21/0x50 > > > [] __kmalloc_track_caller+0x140/0x2b0 > > > [] kstrdup+0x35/0x70 > > > [] acpi_set_pnp_ids+0xd0/0x304 > > > [] acpi_scan_init_hotplug+0x47/0xa1 > > > [] acpi_bus_check_add+0x66/0xd7 > > > [] acpi_ns_walk_namespace+0xb9/0x173 > > > [] acpi_walk_namespace+0x93/0xc6 > > > [] acpi_bus_scan+0x48/0x9a > > > [] acpi_scan_init+0x57/0x14b > > > [] acpi_init+0x244/0x286 > > > [] do_one_initcall+0x10a/0x160 > > > [] kernel_init_freeable+0x103/0x192 > > > [] kernel_init+0x9/0xf0 > > > [] ret_from_fork+0x7c/0xb0 > > > [] 0xffffffffffffffff > > > > > > All four were allocated early in the bootup, and are the only leaks reported in > > > my system. I have not yet tested to see if they are false. > > > > This looks to me like a real leak, possibly introduced by commit > > 6b772e8f9 (ACPI: Update PNPID match handling for notify). The > > acpi_scan_init_hotplug() function calls acpi_set_pnp_ids() which > > allocates pnp.unique_id (kstrdup()) but for some reason it fails and > > does not set pnp.type.hardware_id. The return does not call > > acpi_free_pnp_ids() which would be responsible for such freeing. > > I agree with your analysis. It appears that this ACPI device object has > _UID but not _HID. ACPI spec defines that _UID is a unique ID among a > same _HID. So, it is odd to have _UID without _HID. But, nonetheless, > this case needs to be handled as such systems exist. > > > Something like below, but not tested and may fail some NULL pointer > > checks: > > The change looks good. acpi_free_pnp_ids() handles this empty list > pnp->ids properly. Are you going to submit this patch with your > signed-off? Yes, I'll post it shortly. But I'd like an acked/tested-by as I don't have a platform to test it. Thanks. -- Catalin -- 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/