linux-kernel - Re: [PATCH] mm/kmemleak: add support for re-enable kmemleak at runtime

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: <20140117120436.GC28895@arm.com>
Date:	Fri, 17 Jan 2014 12:04:36 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Jianguo Wu <wujianguo@...wei.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"rob@...dley.net" <rob@...dley.net>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	Li Zefan <lizefan@...wei.com>, Wang Nan <wangnan0@...wei.com>
Subject: Re: [PATCH] mm/kmemleak: add support for re-enable kmemleak at
 runtime

On Fri, Jan 17, 2014 at 09:40:02AM +0000, Jianguo Wu wrote:
> Now disabling kmemleak is an irreversible operation, but sometimes
> we may need to re-enable kmemleak at runtime. So add a knob to enable
> kmemleak at runtime:
> echo on > /sys/kernel/debug/kmemleak

It is irreversible for very good reason: once it missed the initial
memory allocations, there is no way for kmemleak to build the object
reference graph and you'll get lots of false positives, pretty much
making it unusable.

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