From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751094AbcFGEGL (ORCPT ); Tue, 7 Jun 2016 00:06:11 -0400 Received: from mail-oi0-f66.google.com ([209.85.218.66]:34148 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750795AbcFGEGI (ORCPT ); Tue, 7 Jun 2016 00:06:08 -0400 Subject: Re: kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch") To: Catalin Marinas , Christoph Hellwig References: <20160606112620.GA29910@e104818-lin.cambridge.arm.com> <20160606141334.GA6579@lst.de> <20160606161245.GC29910@e104818-lin.cambridge.arm.com> Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Jens Axboe , bart.vanassche@sandisk.com, drysdale@google.com From: Larry Finger Message-ID: <5756482D.2040505@lwfinger.net> Date: Mon, 6 Jun 2016 23:06:05 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <20160606161245.GC29910@e104818-lin.cambridge.arm.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/06/2016 11:12 AM, Catalin Marinas wrote: > On Mon, Jun 06, 2016 at 04:13:34PM +0200, Christoph Hellwig wrote: >> 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. > > I think the reported leaks settle after about 10-20min (2-3 kmemleak > periodic scans), so checking /proc/slabinfo may not be sufficient if > the leak is not growing. The leaks also do not seem to disappear, > otherwise kmemleak would no longer report them (e.g. after kfree, even > if they had been previously reported). 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. Larry