| 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: <53266854.5080605@huawei.com> Date: Mon, 17 Mar 2014 11:13:24 +0800 From: Li Zefan <lizefan@...wei.com> To: Catalin Marinas <catalin.marinas@....com> CC: Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org> Subject: Re: [PATCH 1/3] kmemleak: allow freeing internal objects after disabling kmemleak On 2014/3/13 20:14, Catalin Marinas wrote: > On Thu, Mar 13, 2014 at 06:47:46AM +0000, Li Zefan wrote: >> +Freeing kmemleak internal objects >> +--------------------------------- >> + >> +To allow access to previosuly found memory leaks even when an error fatal >> +to kmemleak happens, internal kmemleak objects won't be freed when kmemleak >> +is disabled, and those objects may occupy a large part of physical >> +memory. >> + >> +If you want to make sure they're freed before disabling kmemleak: >> + >> + # echo scan=off > /sys/kernel/debug/kmemleak >> + # echo off > /sys/kernel/debug/kmemleak > > I would actually change the code to do a stop_scan_thread() as part of > the "off" handling so that scan=off is not required (we can't put it as > part of the kmemleak_disable because we need scan_mutex held). > Sounds reasonable. -- 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