linux-kernel - /proc/slab_allocators question

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <8D11D7DFDC0DCD5-1BF8-2054F@webmail-va038.sysops.aol.com>
Date:	Thu, 3 Apr 2014 14:02:20 -0400 (EDT)
From:	Pietro Paolini <pulsarpietro@....com>
To:	linux-kernel@...r.kernel.org
Subject: /proc/slab_allocators question

 Hello everyone,

I am experiencing a problem where the system reboot due low memory 
conditions and looking at the
/proc/slabinfo

I am able to see that a lot of memory is being used by the size-1024 
cache name which reports a high number of active objects, then
in order to debug this situation I tried to compile with :

CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y

Now I am able to cat the /proc/slab_allocators leaf but that name, nor 
either all the size-* - are present
in that output, I guess because that memory is used by the kmalloc() 
functions.

Than how can I trace who allocates  all that memory in my system ?

Best Regards,
Pietro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/