kmemleak report in 3.9.5 related to ext4_alloc_inode

Hello!

I see this kmemleak report in a slightly modified 3.9.5 kernel (no patches to the ext4 subsystem).

Any idea if this is real and/or what a fix would be?

unreferenced object 0xffff8801170bb700 (size 40):
comm "prelink", pid 25152, jiffies 4352882167 (age 29213.208s) hex dump (first 32 bytes):

    80 cb 94 15 01 88 ff ff d0 4f 4d 18 01 88 ff ff  .........OM.....
    01 00 00 00 00 00 00 00 40 4d 3a 18 01 88 ff ff  ........@M:.....
  backtrace:
    [<ffffffff815de7bf>] kmemleak_alloc+0x73/0x98
    [<ffffffff8118b4d4>] slab_post_alloc_hook+0x28/0x2a
    [<ffffffff8118d9a7>] kmem_cache_alloc+0xb2/0x123
    [<ffffffff81316919>] __debug_object_init+0x43/0x35f
    [<ffffffff81316c62>] debug_object_init+0x14/0x16
    [<ffffffff810b296c>] __init_work+0x27/0x29
    [<ffffffff81241371>] ext4_alloc_inode+0x173/0x1cb
    [<ffffffff811b0db4>] alloc_inode+0x1d/0x78
    [<ffffffff811b0e7c>] iget_locked+0x6d/0x12f
    [<ffffffff81229817>] ext4_iget+0x2c/0x932
    [<ffffffff8122f485>] ext4_lookup+0xd2/0x12a
    [<ffffffff811a3556>] lookup_real+0x2c/0x47
    [<ffffffff811a3e0c>] __lookup_hash+0x33/0x3c
    [<ffffffff811a5897>] walk_component+0x73/0x171
    [<ffffffff811a6e2c>] path_lookupat+0xa7/0x304
    [<ffffffff811a70b4>] filename_lookup+0x2b/0x82

Thanks,
Ben

Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

I now think this is bogus. I disabled SLUB debugging and other debugging options and now I no longer see this reported by kmemleak.

Thanks,
Ben

Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com