On Sat, Sep 5, 2009 at 2:27 AM, Johannes Berg<johannes@xxxxxxxxxxxxxxxx> wrote: > On Fri, 2009-09-04 at 15:15 -0700, Luis R. Rodriguez wrote: >> I get these with today's wireless-testing + pulling Catalin's kmemleak >> tree. I nothing upon bootup, and then after a while I force a scan and >> get (besides some other acpi stuff): >> >> unreferenced object 0xffff880039c7d700 (size 256): >> comm "events/1", pid 10, jiffies 4295050369 >> hex dump (first 32 bytes): >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ >> backtrace: >> [<ffffffff814e9d55>] kmemleak_alloc+0x25/0x60 >> [<ffffffff81118a83>] kmem_cache_alloc_node+0x193/0x200 >> [<ffffffff8141dc6a>] __alloc_skb+0x4a/0x180 >> [<ffffffff814ddb82>] wireless_send_event+0x1f2/0x410 > > Do you have CONFIG_COMPAT? Indeed, CONFIG_COMPAT=y > And if you do, can you figure out whether > this is "skb" or "compskb"? How would I do that? 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
