On Thu, Nov 12, 2009 at 11:35 AM, 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. You need a kernel with debugging too to get a good valuable trace. 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
