linux-kernel - Re: kmemleak report after 9082e87bfbf8 ("block: remove struct bio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160607063621.GA12718@lst.de>
Date:	Tue, 7 Jun 2016 08:36:21 +0200
From:	Christoph Hellwig <hch@....de>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	Christoph Hellwig <hch@....de>, linux-block@...r.kernel.org,
	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...com>,
	bart.vanassche@...disk.com, drysdale@...gle.com
Subject: Re: kmemleak report after 9082e87bfbf8 ("block: remove struct
	bio_batch")

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?