| 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
| ||
|
Message-Id: <1229507096.32517.8.camel@pc1117.cambridge.arm.com> Date: Wed, 17 Dec 2008 09:44:56 +0000 From: Catalin Marinas <catalin.marinas@....com> To: paulmck@...ux.vnet.ibm.com Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...helsinki.fi>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH 01/15] kmemleak: Add the base support On Tue, 2008-12-16 at 11:36 -0800, Paul E. McKenney wrote: > On Wed, Dec 10, 2008 at 06:26:59PM +0000, Catalin Marinas wrote: > > This patch adds the base support for the kernel memory leak > > detector. It traces the memory allocation/freeing in a way similar to > > the Boehm's conservative garbage collector, the difference being that > > the unreferenced objects are not freed but only shown in > > /sys/kernel/debug/memleak. Enabling this feature introduces an > > overhead to memory allocations. > > Looks good to me from an RCU viewpoint! > > Reviewed-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com> Thanks for reviewing it. FYI, in the version I'm going to post this week I added another mutex to ensure the exclusive opening of the /sys/kernel/debug/memleak file as one can now use this file to configure kmemleak at run-time. The RCU locking isn't affected and I'll add your "Reviewed-by:" line. -- 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/
Powered by blists - more mailing lists