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, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>