From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Dave Jones <davej@codemonkey.org.uk>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: blk-mq vs kmemleak
Date: Wed, 8 Jul 2015 01:17:40 -0700 [thread overview]
Message-ID: <20150708081740.GA3374@infradead.org> (raw)
In-Reply-To: <559BDB49.70209@sandisk.com>
On Tue, Jul 07, 2015 at 06:59:37AM -0700, Bart Van Assche wrote:
> Please note that my test was run with CONFIG_SLUB_DEBUG=y which causes a red
> zone to be allocated before and after each block of allocated memory. Could
> that explain the kmalloc-96 objects ?
96 is almost guaranteed to be the sense buffer allocated in
scsi_init_request and freed in scsi_exit_request.
next prev parent reply other threads:[~2015-07-08 8:17 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 [this message]
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=20150708081740.GA3374@infradead.org \
--to=hch@infradead.org \
--cc=bart.vanassche@sandisk.com \
--cc=catalin.marinas@arm.com \
--cc=davej@codemonkey.org.uk \
--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.