From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753552AbcFGGgf (ORCPT ); Tue, 7 Jun 2016 02:36:35 -0400 Received: from verein.lst.de ([213.95.11.211]:43438 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753482AbcFGGge (ORCPT ); Tue, 7 Jun 2016 02:36:34 -0400 Date: Tue, 7 Jun 2016 08:36:21 +0200 From: Christoph Hellwig To: Larry Finger Cc: Catalin Marinas , Christoph Hellwig , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Jens Axboe , bart.vanassche@sandisk.com, drysdale@google.com Subject: Re: kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch") Message-ID: <20160607063621.GA12718@lst.de> References: <20160606112620.GA29910@e104818-lin.cambridge.arm.com> <20160606141334.GA6579@lst.de> <20160606161245.GC29910@e104818-lin.cambridge.arm.com> <5756482D.2040505@lwfinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5756482D.2040505@lwfinger.net> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 06, 2016 at 11:06:05PM -0500, Larry Finger wrote: > The leak is definitely not related to mkfs. At the moment, my system has > been up about 26 hours, and has generated 162 of these leaks without ever > doing a single mkfs. In addition, the box say idle for almost 12 of those > hours. That makes sense only if you are using ext4 that's doing discards/write_zero at runtime. Either way, can you please give the patch from Shaun a try?