Messages in this thread | | | Date | Thu, 13 Mar 2014 12:14:59 +0000 | From | Catalin Marinas <> | Subject | Re: [PATCH 1/3] kmemleak: allow freeing internal objects after disabling kmemleak |
| |
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
| |