On Thu, 16 May 2019, Qian Cai wrote:
> It turned out that DEBUG_SLAB_LEAK is still broken even after recent
> recue efforts that when there is a large number of objects like
> kmemleak_object which is normal on a debug kernel,
Acked-by: Christoph Lameter
On Thu, May 16, 2019 at 12:58 PM Qian Cai wrote:
>
> Also, since it seems no one had noticed when it was totally broken
> more than 2-year ago - see the commit fcf88917dd43 ("slab: fix a crash
> by reading /proc/slab_allocators"), probably nobody cares about it
> anymore due to the decline of the
It turned out that DEBUG_SLAB_LEAK is still broken even after recent
recue efforts that when there is a large number of objects like
kmemleak_object which is normal on a debug kernel,
# grep kmemleak /proc/slabinfo
kmemleak_object 2243606 3436210 ...
reading /proc/slab_allocators could easi
3 matches
Mail list logo