lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210118074913.GA39161@mtl-vdi-166.wap.labs.mlnx>
Date:   Mon, 18 Jan 2021 09:49:13 +0200
From:   Eli Cohen <elic@...dia.com>
To:     Christian König <christian.koenig@....com>
CC:     Thomas Zimmermann <tzimmermann@...e.de>,
        <virtualization@...ts.linux-foundation.org>,
        <linux-kernel@...r.kernel.org>, <daniel.vetter@...ll.ch>,
        <sam@...nborg.org>, dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: Change eats memory on my server

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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ