From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754953AbcFGK06 (ORCPT ); Tue, 7 Jun 2016 06:26:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47444 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752579AbcFGK04 (ORCPT ); Tue, 7 Jun 2016 06:26:56 -0400 Date: Tue, 7 Jun 2016 18:26:51 +0800 From: Xiong Zhou To: linux-block@vger.kernel.org, hch@lst.de, axboe@kernel.dk Cc: David Drysdale , Xiong Zhou , Stephen Rothwell , axboe@fb.com, linux-next@vger.kernel.org, linux-nvdimm@ml01.01.org, "linux-kernel@vger.kernel.org" , Christoph Hellwig Subject: Re: linux-next/linux memleak after IO on dax mountpoint Message-ID: <20160607102651.GA6480@dhcp12-144.nay.redhat.com> References: <20160527084617.GD2933@dhcp12-144.nay.redhat.com> <20160528040554.GA23685@dhcp12-144.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Tue, 07 Jun 2016 10:26:55 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org adding block-list On Fri, Jun 03, 2016 at 09:48:27AM -0700, Bart Van Assche wrote: > On 06/02/2016 08:22 AM, David Drysdale wrote: > > FWIW, I'm also seeing kmemleak report a leak with v4.7-rc1, in > > a different scenario (just normal desktop use). Not done much > > digging so far, but this commit (9082e87bf) looks like it might be > > relevant -- lots of the following: > > > > unreferenced object 0xffff8800c288e900 (size 256): > > comm "dconf-service", pid 1461, jiffies 4294895636 (age 48.028s) > > hex dump (first 32 bytes): > > 00 00 00 00 00 00 00 00 c0 a4 c0 c6 00 88 ff ff ................ > > 02 20 00 20 00 00 00 00 11 00 00 00 00 00 00 00 . . ............ > > backtrace: > > [] kmemleak_alloc+0x28/0x50 > > [] kmem_cache_alloc+0xfc/0x360 > > [] mempool_alloc_slab+0x15/0x20 > > [] mempool_alloc+0x6e/0x170 > > [] bio_alloc_bioset+0xb8/0x230 > > [] next_bio+0x24/0x50 > > [] blkdev_issue_zeroout+0xdf/0x1d0 > > [] ext4_issue_zeroout+0x39/0x50 > > [] ext4_ext_zeroout+0x2f/0x40 > > [] ext4_ext_map_blocks+0x1870/0x2190 > > [] ext4_map_blocks+0x111/0x620 > > [] ext4_writepages+0x7c8/0x10a0 > > [] do_writepages+0x21/0x30 > > [] __filemap_fdatawrite_range+0xaa/0xf0 > > [] filemap_write_and_wait_range+0x2d/0x70 > > [] ext4_sync_file+0x18d/0x500 > > (+Christoph) > > With kernel v4.7-rc1 and XFS I see that the blkdev_issue_zeroout() calls > triggered by xfstests make kmemleak complain. I hadn't seen this with any > previous kernel version. > > Bart. unreferenced object 0xffff880c4bce2800 (size 2048): comm "dbench", pid 11389, jiffies 4294884573 (age 193.194s) hex dump (first 32 bytes): c0 1d 09 00 00 ea ff ff 00 10 00 00 00 00 00 00 ................ c0 1d 09 00 00 ea ff ff 00 10 00 00 00 00 00 00 ................ backtrace: [] kmemleak_alloc+0x4e/0xb0 [] kmem_cache_alloc+0xc3/0x200 [] bvec_alloc+0x5c/0xf0 [] bio_alloc_bioset+0x1ce/0x2d0 [] next_bio+0x24/0x50 [] blkdev_issue_zeroout+0xe0/0x1d0 [] ext4_issue_zeroout+0x38/0x50 [ext4] [] ext4_map_blocks+0x39e/0x640 [ext4] [] _ext4_get_block+0x93/0xf0 [ext4] [] ext4_get_block_trans+0xbf/0x110 [ext4] [] ext4_dax_get_block+0x25/0x70 [ext4] [] dax_do_io+0x446/0x610 [] ext4_direct_IO+0x494/0x750 [ext4] [] generic_file_direct_write+0xb0/0x180 [] __generic_file_write_iter+0xbd/0x1e0 [] ext4_file_write_iter+0xf7/0x330 [ext4]