On 07/07/15 03:33, Catalin Marinas wrote:
On Fri, Jul 03, 2015 at 06:04:00PM +0100, Bart Van Assche wrote:
A few weeks ago I had noticed similar kmemleak reports.
However, when I reran my test with kmemleak disabled memory usage was
stable. See also
https://www.redhat.com/archives/dm-devel/2015-May/msg00198.html.
Further down in this thread it gets interesting with kmalloc-96 objects
disappearing in /proc/slabinfo with kmemleak disabled. Kmemleak does not
allocate such objects, the two types it allocates are in separate
kmem_cache as kmemleak_object and kmemleak_scan_area. However, the 96
size is reported by kmemleak as well, so maybe it was fixed by some
other patch in the meantime?
If you manage to reproduce it again please let me know. Thanks.
Hello Catalin,
Please note that my test was run with CONFIG_SLUB_DEBUG=y which causes a
red zone to be allocated before and after each block of allocated
memory. Could that explain the kmalloc-96 objects ?
Thanks,
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
