Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751466AbWHSKHI (ORCPT ); Sat, 19 Aug 2006 06:07:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751696AbWHSKHI (ORCPT ); Sat, 19 Aug 2006 06:07:08 -0400 Received: from py-out-1112.google.com ([64.233.166.180]:65491 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S1751688AbWHSKHG (ORCPT ); Sat, 19 Aug 2006 06:07:06 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JP40kBPfYQKYplZxAdTb8dKwCssUZX4o8Vum20EsTvaJFcxif4mATbFAXhqjrtsFLF0h9zqqC8EHqZLP/0aZZ2nd0JDbMTbm15cHMJlvLBCNrlKpmr89iuu3sWOpslJ+Gx/e+XaLj70vAL82A/HGQbcpq3wkEzv0dbG5dbzZ3lA= Message-ID: Date: Sat, 19 Aug 2006 11:07:04 +0100 From: "Catalin Marinas" To: "Michal Piotrowski" , "Antonino A. Daplas" Subject: Re: [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9 Cc: linux-kernel@vger.kernel.org In-Reply-To: <6bffcb0e0608181549o3034398fob3763d3ce0869cfe@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060812215857.17709.79502.stgit@localhost.localdomain> <6bffcb0e0608180655j50332247m8ed393c37d570ee4@mail.gmail.com> <6bffcb0e0608180715v27015481vb7c603c4be356a21@mail.gmail.com> <6bffcb0e0608180942l12e342epd60dffbb5c5d4b3e@mail.gmail.com> <6bffcb0e0608181438m3406de08q9a168d486127aef@mail.gmail.com> <6bffcb0e0608181549o3034398fob3763d3ce0869cfe@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1241 Lines: 38 On 18/08/06, Michal Piotrowski wrote: > I just added your "Fix memory leak in vc_resize/vc_allocate" patch to > my series file. > > orphan pointer 0xc6110000 (size 12288): > c017480e: <__kmalloc> > c024dda4: > c020ed9c: > c0251028: > c02511e0: > c020e21e: > c0212b08: > c0212ce1: > orphan pointer 0xf55b0000 (size 8208): > c017480e: <__kmalloc> > c0211bb8: > c0251b17: > c0251c7b: > c0249a97: > c024432e: > c0189fd1: > c018a269: The second one is probably a false positive as the stored pointer is different from the one returned by kmalloc (there is some padding). I'll add it to the kmemleak-false-positives patch. The first one might be a real leak. Anotonino, any idea about this? 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/