All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: blk-mq vs kmemleak
Date: Fri, 3 Jul 2015 13:07:17 -0400	[thread overview]
Message-ID: <20150703170717.GA10928@codemonkey.org.uk> (raw)
In-Reply-To: <5596C080.4050009@sandisk.com>

On Fri, Jul 03, 2015 at 10:04:00AM -0700, Bart Van Assche wrote:
 > On 07/03/15 09:11, Dave Jones wrote:
 > > After a fuzzing run recently, I noticed that the machine had oom'd, and
 > > killed everything, but there was still 3GB of memory still in use, that
 > > I couldn't even reclaim with /proc/sys/vm/drop_caches
 > > ...
 > > I'm wondering if there's just some annotation missing to appease kmemleak,
 > > because I'm seeing thousands of these.
 > >
 > > Or it could be a real leak, but it seems surprising no-one else is complaining.
 > 
 > Dave, with which kernel version has this behavior been observed ?

Linus' current tree

	Dave


  reply	other threads:[~2015-07-03 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 16:11 blk-mq vs kmemleak Dave Jones
2015-07-03 17:04 ` Bart Van Assche
2015-07-03 17:07   ` Dave Jones [this message]
2015-07-07 10:33   ` Catalin Marinas
2015-07-07 13:59     ` Bart Van Assche
2015-07-08  8:17       ` Christoph Hellwig
2015-08-01  0:37         ` Bart Van Assche
2015-08-03 10:43           ` Catalin Marinas
2015-08-03 13:33             ` Christoph Hellwig
2015-08-03 15:34               ` Catalin Marinas
2015-08-03 17:05             ` Bart Van Assche
2015-08-03 17:50               ` Catalin Marinas

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=20150703170717.GA10928@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=bart.vanassche@sandisk.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-scsi@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.