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]

Date:	Mon, 6 Jun 2016 16:13:34 +0200
From:	Christoph Hellwig <hch@....de>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	Christoph Hellwig <hch@....de>, linux-block@...r.kernel.org,
	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...com>,
	Larry.Finger@...inger.net, bart.vanassche@...disk.com,
	drysdale@...gle.com
Subject: Re: kmemleak report after 9082e87bfbf8 ("block: remove struct
	bio_batch")

Hi Catalin,

I've got a few reports of this over the weekend, but it still doesn't
make much sense to me.

Could it be that kmemleak can't deal with the bio_batch logic?  I've
tried to look at the various bio and biovec number entries in
/proc/slabinfo, and while they keep changing a bit during the
system runtime there doesn't seem to be a persistent increase
even after lots of mkfs calls.

Can all of you who have reported the issue take a look at their
slabinfo files and check if you can confirm that observation?