3.4-rc2: Possible memory leak in __register_sysctl_table()

[Larry Finger]

I am seeing apparent memory leaks in 3.4-rcX. I do not think I saw these in 3.3.

The kmemleak traceback is:

unreferenced object 0xffff8800b7536180 (size 96):
  comm "swapper/0", pid 1, jiffies 4294892617 (age 8756.084s)
  hex dump (first 32 bytes):
    20 c4 1c 82 ff ff ff ff 00 00 00 00 01 00 00 00   ...............
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff81383401>] kmemleak_alloc+0x21/0x50
    [<ffffffff81134153>] __kmalloc+0x123/0x2a0
    [<ffffffff811a8ac2>] __register_sysctl_table+0x62/0x4d0
    [<ffffffff811a907d>] register_leaf_sysctl_tables+0x14d/0x220
    [<ffffffff811a90e4>] register_leaf_sysctl_tables+0x1b4/0x220
    [<ffffffff811a92c9>] __register_sysctl_paths+0x159/0x1f0
    [<ffffffff811a9376>] register_sysctl_paths+0x16/0x20
    [<ffffffff816b5c41>] ip_static_sysctl_init+0x17/0x19
    [<ffffffff816b68bc>] inet_init+0xb4/0x2b2
    [<ffffffff810001ca>] do_one_initcall+0x3a/0x170
    [<ffffffff81686c52>] kernel_init+0xf7/0x17b
    [<ffffffff8139f154>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff

Thanks,

Larry
--
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/