On Thu, Nov 12, 2009 at 02:16:09PM -0800, Matteo Croce wrote: > On Thu, Nov 12, 2009 at 8:35 PM, Luis R. Rodriguez > <lrodriguez@xxxxxxxxxxx> wrote: > > On Thu, Nov 12, 2009 at 11:31 AM, Johannes Berg > > <johannes@xxxxxxxxxxxxxxxx> wrote: > >> On Thu, 2009-11-12 at 20:18 +0100, Matteo Croce wrote: > >> > >>> # echo scan >/sys/kernel/debug/kmemleak ; cat > >>> /sys/kernel/debug/kmemleak > >>> kmemleak: 197 new suspected memory leaks (see /sys/kernel/debug/kmemleak) > >>> unreferenced object 0xc5cfea80 (size 192): > >>> comm "softirq", pid 0, jiffies 14191 > >>> backtrace: > >>> [<ffffffff>] 0xffffffff > >> > >> that's kinda useless, can you run > > > > But if you insist on using kmemleak, try clearing the list > > > > echo clear > kmemleak > > > > Then scan > > > > echo scan > kmemleak > > > > then run your frame injection tests and then re-run scan. > > > > echo scan > kmemleak > > > > Then paste the output here. > > > > Luis > > > > root@alix:/sys/kernel/debug# rmmod inject > inject_exit Inject, exiting module > root@alix:/sys/kernel/debug# echo clear > kmemleak I forgot you're on 2.6.31, clear stuff was added to kmemleak for 2.6.32. > root@alix:/sys/kernel/debug# echo scan >kmemleak > kmemleak: 61037 new suspected memory leaks (see /sys/kernel/debug/kmemleak) > root@alix:/sys/kernel/debug# modprobe inject > inject_init Inject, inserting module > inject_init Inject, initializing the timer > root@alix:/sys/kernel/debug# echo scan >kmemleak > root@alix:/sys/kernel/debug# cat kmemleak > unreferenced object 0xccd48e70 (size 64): What's 0xccd48e70 and friends? Can you enable debugging on your kernel? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
