> Is the obj_pool in lib/debugobjects.c supposed to be empty at the end of > the test and all objects freed? The obj_pool is a list and the first > elements in this list are from obj_static_pool, which is __initdata. > Objects added to the list may be referred by chaining with the > obj_static_pool objects but kmemleak doesn't scan __initdata as this is > usually freed before kmemleak does its first scan. So, if it is just a > transient "leak", kmemleak should later report "kmemleak: referenced" if > a kmem_cache_free() is called on any of the reported objects.

> You can mount debugfs on /sys/kerne/debug and read the kmemleak file in > there (it triggers a new scan as well).

Currently prints the acpi traces I already posted.

> You can also echo stack=on to > the above kmemleak file to enable kernel stack scanning. > > Could you send me your config options for DEBUG_OBJECTS_* and slab > allocator so I can try to reproduce this?

CONFIG_DEBUG_OBJECTS=y# CONFIG_DEBUG_OBJECTS_SELFTEST is not setCONFIG_DEBUG_OBJECTS_FREE=yCONFIG_DEBUG_OBJECTS_TIMERS=yCONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1