Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932647AbWLMKAH (ORCPT ); Wed, 13 Dec 2006 05:00:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932648AbWLMKAH (ORCPT ); Wed, 13 Dec 2006 05:00:07 -0500 Received: from nz-out-0506.google.com ([64.233.162.226]:57752 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932647AbWLMKAF (ORCPT ); Wed, 13 Dec 2006 05:00:05 -0500 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=SjLzlvtE6+/voJHoD4a+jPhkW7YUd3JrcjPufvX/zvBmjzEXafQmYE45w6D3RtMnNWNm0S9Hiy+gDpd0ihu2oMKYkrcXINDZlnhzxrmJagDXA2xynRVuDW7vdY6NB/cX2nopLEr6WyG/enWJW/pnFbt81ldLuVvM/nswZ8iuVcI= Message-ID: Date: Wed, 13 Dec 2006 10:00:05 +0000 From: "Catalin Marinas" To: "Linux Kernel Mailing List" Subject: Re: Possible memory leak in block/ll_rw_blk.c Cc: "Mike Christie" , "FUJITA Tomonori" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 962 Lines: 30 On 09/12/06, Catalin Marinas wrote: > unreferenced object 0xdd9162b0 (size 64): > [] kmem_cache_alloc > [] mempool_alloc_slab > [] mempool_alloc > [] bio_alloc_bioset > [] bio_alloc > [] bio_copy_user > [] __blk_rq_map_user > [] blk_rq_map_user > [] sg_io > [] scsi_cmd_ioctl > [] sd_ioctl > [] blkdev_driver_ioctl > [] blkdev_ioctl > [] block_ioctl > [] do_ioctl I can confirm that the memory leak disappeared with commit 77d172ce2719b5ad2dc0637452c8871d9cba344c (by Fujita Tomonori). Regards. -- 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/