Re: [2.6.31] Memory leak in load_module()?

Catalin Marinas
2009-09-11T09:29:34Z

Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
> I changed CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE to 2000 and did
>
> # insmod /lib/modules/2.6.31/kernel/drivers/edac/r82600_edac.ko
> insmod: error inserting '/lib/modules/2.6.31/kernel/drivers/edac/r82600_edac.ko': -1 Unknown symbol in module
> # echo scan > /sys/kernel/debug/kmemleak
> # dmesg
> r82600_edac: Unknown symbol edac_mc_del_mc
> r82600_edac: Unknown symbol edac_mc_add_mc
> r82600_edac: Unknown symbol edac_pci_create_generic_ctl
> r82600_edac: Unknown symbol edac_mc_alloc
> r82600_edac: Unknown symbol edac_mc_find_csrow_by_page
> r82600_edac: Unknown symbol edac_mc_free
> r82600_edac: Unknown symbol edac_mc_handle_ce
> r82600_edac: Unknown symbol edac_mc_handle_ue
> r82600_edac: Unknown symbol edac_pci_release_generic_ctl
> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> # tail -n 4 /sys/kernel/debug/kmemleak
> unreferenced object 0xd643a788 (size 32):
> comm "insmod", pid 2854, jiffies 4294791099
> backtrace:
> [<ffffffff>] 0xffffffff
>
> Is this real memory leak?

It could be but isn't stack tracing enabled on your system? The
backtrace doesn't seem very useful.

--
Catalin