All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Christoph Hellwig <hch@lst.de>,
	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: Tue, 7 Jun 2016 08:36:21 +0200	[thread overview]
Message-ID: <20160607063621.GA12718@lst.de> (raw)
In-Reply-To: <5756482D.2040505@lwfinger.net>

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?

      reply	other threads:[~2016-06-07  6:36 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
2016-06-07  6:36       ` Christoph Hellwig [this message]

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=20160607063621.GA12718@lst.de \
    --to=hch@lst.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=axboe@fb.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=catalin.marinas@arm.com \
    --cc=drysdale@google.com \
    --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.