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). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
