[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000014179fc82ac-8e47c69d-8c5a-4f75-957d-15741eb36eda-000000@email.amazonses.com>
Date: Wed, 2 Oct 2013 16:24:53 +0000
From: Christoph Lameter <cl@...ux.com>
To: Catalin Marinas <catalin.marinas@....com>
cc: "Bird, Tim" <Tim.Bird@...ymobile.com>,
Frank Rowand <frowand.list@...il.com>,
Pekka Enberg <penberg@...nel.org>,
Matt Mackall <mpm@...enic.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
"Bobniev, Roman" <Roman.Bobniev@...ymobile.com>,
Andersson, Björn
<Bjorn.Andersson@...ymobile.com>
Subject: Re: [PATCH] slub: Proper kmemleak tracking if CONFIG_SLUB_DEBUG
disabled
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists