Messages in this thread | | | Subject | Re: Change eats memory on my server | From | Christian König <> | Date | Mon, 18 Jan 2021 08:57:26 +0100 |
| |
Am 18.01.21 um 08:49 schrieb Eli Cohen: > On Mon, Jan 18, 2021 at 08:43:12AM +0100, Christian König wrote: >> Hi Eli, >> >> have you already tried using kmemleak? >> >> This sounds like a leak of memory allocated using kmalloc(), so kmemleak >> should be able to catch it. >> > Hi Christian, > > I have the following configured but I did not see any visible complaint > in dmesg. > > CONFIG_HAVE_DEBUG_KMEMLEAK=y > CONFIG_DEBUG_KMEMLEAK=y > CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=16000 > > Any other configuration that I need to set?
As long as you don't have any kernel parameters to enable it I think you need to do "echo scan > /sys/kernel/debug/kmemleak" to start a scan.
The result can then be queried using "cat /sys/kernel/debug/kmemleak".
Regards, Christian.
| |