All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jens Axboe <axboe@fb.com>,
	bart.vanassche@sandisk.com, drysdale@google.com
Subject: Re: kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch")
Date: Mon, 6 Jun 2016 23:06:05 -0500	[thread overview]
Message-ID: <5756482D.2040505@lwfinger.net> (raw)
In-Reply-To: <20160606161245.GC29910@e104818-lin.cambridge.arm.com>

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

  parent reply	other threads:[~2016-06-07  4:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 11:26 kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch") Catalin Marinas
2016-06-06 14:13 ` Christoph Hellwig
2016-06-06 16:12   ` Catalin Marinas
2016-06-06 17:09     ` Shaun Tancheff
2016-06-06 17:27       ` Christoph Hellwig
2016-06-06 17:35         ` Catalin Marinas
2016-06-06 18:15         ` Jens Axboe
2016-06-07  9:39       ` Catalin Marinas
2016-06-07 14:18         ` Larry Finger
2016-06-07 15:43           ` David Drysdale
2016-06-07  4:06     ` Larry Finger [this message]
2016-06-07  6:36       ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5756482D.2040505@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=axboe@fb.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=catalin.marinas@arm.com \
    --cc=drysdale@google.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.