From: Christoph Lameter <cl@linux.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "Bird, Tim" <Tim.Bird@sonymobile.com>,
"Frank Rowand" <frowand.list@gmail.com>,
"Pekka Enberg" <penberg@kernel.org>,
"Matt Mackall" <mpm@selenic.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
"Bobniev, Roman" <Roman.Bobniev@sonymobile.com>,
"Andersson, Björn" <Bjorn.Andersson@sonymobile.com>
Subject: Re: [PATCH] slub: Proper kmemleak tracking if CONFIG_SLUB_DEBUG disabled
Date: Wed, 2 Oct 2013 16:24:53 +0000 [thread overview]
Message-ID: <0000014179fc82ac-8e47c69d-8c5a-4f75-957d-15741eb36eda-000000@email.amazonses.com> (raw)
In-Reply-To: <20131002155417.GB29794@arm.com>
On Wed, 2 Oct 2013, Catalin Marinas wrote:
> Kmemleak doesn't depend on SLUB_DEBUG (at least it didn't originally ;),
> so I don't think we should add an artificial dependency (or select). Can
> we have kmemleak_*() calls in both debug and !debug hooks?
Yes if you move the hook calls out from under CONFIG_SLUB_DEBUG.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-10-02 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 20:38 Frank Rowand
2013-09-30 9:04 ` Catalin Marinas
2013-10-02 14:41 ` Christoph Lameter
2013-10-02 15:33 ` Bird, Tim
2013-10-02 15:54 ` Catalin Marinas
2013-10-02 16:24 ` Christoph Lameter [this message]
2013-10-02 15:57 ` Christoph Lameter
2013-10-02 16:25 ` Catalin Marinas
2013-10-08 22:37 [PATCH] slub: proper " Tim Bird
2013-10-08 22:58 Tim Bird
2013-10-09 13:28 ` Catalin Marinas
2013-10-09 19:07 ` Christoph Lameter
2013-10-23 11:52 ` Bobniev, Roman
2013-10-24 17:20 ` Pekka Enberg
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=0000014179fc82ac-8e47c69d-8c5a-4f75-957d-15741eb36eda-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=Roman.Bobniev@sonymobile.com \
--cc=Tim.Bird@sonymobile.com \
--cc=catalin.marinas@arm.com \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox