[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200909112108.EGE48990.SLJFQHMFtOVFOO@I-love.SAKURA.ne.jp>
Date: Fri, 11 Sep 2009 21:08:03 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: catalin.marinas@....com
Cc: rusty@...tcorp.com.au, linux-kernel@...r.kernel.org
Subject: Re: [2.6.31] Memory leak in load_module()?
Catalin Marinas wrote:
> The object above was allocated by kstrdup via setup_modinfo_srcversion
> but the module loading failed and no other kernel part freed the
> mod->filed object. I think it's a real leak but you could try a few
> "echo scan" to make sure it's not just a temporary false positive.
I did
while : ; do insmod /lib/modules/2.6.31/kernel/drivers/edac/r82600_edac.ko; sleep 1; echo scan > /sys/kernel/debug/kmemleak ; sleep 10; dmesg -c; done
and verified that
kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
message appars everytime. This is unlikely temporary false positive.
unreferenced object 0xdeb89408 (size 32):
comm "insmod", pid 2969, jiffies 1406494
unreferenced object 0xde842750 (size 32):
comm "insmod", pid 2989, jiffies 1514442
unreferenced object 0xde842a60 (size 32):
comm "insmod", pid 2993, jiffies 1526889
unreferenced object 0xdeb89440 (size 32):
comm "insmod", pid 2999, jiffies 1539244
I'll wait for maintainer's response.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists