Re: kmemleak errors

[Catalin Marinas]

Peter Teoh <htmldeveloper@xxxxxxxxx> wrote:
> cat /sys/kernel/debug/kmemleak gave:
>
> unreferenced object 0xffff8800bd864000 (size 40):
>   comm "swapper", pid 0, jiffies 4294937296
>   hex dump (first 32 bytes):
>     00 00 00 00 00 00 00 00 70 40 86 bd 00 88 ff ff  ........p@......
>     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>   backtrace:
>     [<ffffffff81ef55b6>] kmemleak_alloc+0x73/0xd8
>     [<ffffffff81154d66>] kmem_cache_alloc+0xf7/0x15a
>     [<ffffffff82b2b88a>] debug_objects_mem_init+0x71/0x234
>     [<ffffffff82afef26>] start_kernel+0x356/0x414
>     [<ffffffff82afe2a9>] x86_64_start_reservations+0xb9/0xd4
>     [<ffffffff82afe3b2>] x86_64_start_kernel+0xee/0x109
>     [<ffffffffffffffff>] 0xffffffffffffffff

If run

  echo scan > /sys/kernel/debug/kmemleak

a few times, do they disappear? I think the debug_objects reports are
false positives but couldn't figure why kmemleak cannot track
them. I'll look again at them and maybe add an annotation
(kmemleak_not_leak).

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