All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Dave Jones <davej@codemonkey.org.uk>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: blk-mq vs kmemleak
Date: Mon, 3 Aug 2015 10:05:59 -0700	[thread overview]
Message-ID: <55BF9F77.90906@sandisk.com> (raw)
In-Reply-To: <20150803104309.GB4033@e104818-lin.cambridge.arm.com>

On 08/03/2015 03:43 AM, Catalin Marinas wrote:
> The pages allocated for struct request contain pointers to other slab
> allocations (via ops->init_request). Since kmemleak does not track/scan
> page allocations, the slab objects will be reported as leaks (false
> positives). This patch adds kmemleak callbacks to allow tracking of such
> pages.
>
> Signed-off-by: Catalin Marinas<catalin.marinas@arm.com>
> Reported-by: Bart Van Assche<bart.vanassche@sandisk.com>

That patch works fine on my test setup, hence:

Tested-by: Bart Van Assche<bart.vanassche@sandisk.com>

Thanks !

Bart.

  parent reply	other threads:[~2015-08-03 17:06 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
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 [this message]
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=55BF9F77.90906@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=catalin.marinas@arm.com \
    --cc=davej@codemonkey.org.uk \
    --cc=hch@infradead.org \
    --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.