Thread (3 messages) 3 messages, 2 authors, 2021-11-26

Re: [PATCH] mm: kmemleak: alloc gray object for reserved region with direct map.

From: Calvin Zhang <hidden>
Date: 2021-11-26 01:37:44
Also in: linux-devicetree, lkml

On Thu, Nov 25, 2021 at 05:17:53PM +0000, Catalin Marinas wrote:
On Tue, Nov 23, 2021 at 05:06:41PM +0800, Calvin Zhang wrote:
quoted
Reserved regions with direct mapping may contain references to other
regions. CMA region with fixed location is reserved without creating
kmemleak_object for it.

So add them as gray kmemleak objects.
Do you get any kmemleak false positives without this patch? It would be
good to include them in the commit message.
Sorry, no. I thought it was possible before I saw this commit:
620951e27457 ("mm/cma: make kmemleak ignore CMA regions"). 
Without seeing a false positive caused by this, I'm not convinced it is
the right approach. You mentioned CMA but telling kmemleak about the
whole CMA region is a pretty big hammer. I'd rather add individual
kmemleak_alloc_*() calls in cma_alloc().
Yeah, I agree.

--
Calvin

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help