lkml.org 
[lkml]   [2021]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Change eats memory on my server
From
Date
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.

\
 
 \ /
  Last update: 2021-01-18 09:00    [W:0.095 / U:0.816 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site