linux-kernel - Re: [PATCH v3 0/5] kmemleak: few small cleanups and clear command support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1252344570.23780.110.camel@pc1117.cambridge.arm.com>
Date:	Mon, 07 Sep 2009 18:29:30 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	penberg@...helsinki.fi, mcgrof@...il.com
Subject: Re: [PATCH v3 0/5] kmemleak: few small cleanups and clear command
	support

On Fri, 2009-09-04 at 17:44 -0700, Luis R. Rodriguez wrote:
> Here is my third respin, this time rebased ontop of:
> 
> git://linux-arm.org/linux-2.6 kmemleak
> 
> As suggested by Catalin we now clear the list by only painting reported
> unreferenced objects and the color we use is grey to ensure future
> scans are possible on these same objects to account for new allocations
> in the future referenced on the cleared objects.
> 
> Patch 3 is now a little different, now with a paint_ptr() and
> a __paint_it() helper.

Thanks for the patches. They look ok now, I'll merge them tomorrow to my
kmemleak branch and give them a try.

> I tested this by clearing kmemleak after bootup, then writing my
> own buggy module which kmalloc()'d onto some internal pointer,
> scanned, unloaded, and scanned again and then saw a new shiny
> report come up:

BTW, kmemleak comes with a test module which does this.

-- 
Catalin

--
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/