* kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree
@ 2009-09-04 22:15 Luis R. Rodriguez
2009-09-04 22:32 ` Catalin Marinas
2009-09-05 9:27 ` Johannes Berg
0 siblings, 2 replies; 5+ messages in thread
From: Luis R. Rodriguez @ 2009-09-04 22:15 UTC (permalink / raw)
To: linux-wireless, Catalin Marinas
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
[<ffffffffa01b7084>] ___cfg80211_scan_done+0xe4/0x110 [cfg80211]
[<ffffffffa01b70d6>] __cfg80211_scan_done+0x26/0x50 [cfg80211]
[<ffffffff8106de80>] worker_thread+0x1d0/0x380
[<ffffffff81073266>] kthread+0xa6/0xb0
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff8800322bd000 (size 4096):
comm "events/1", pid 10, jiffies 4295050369
hex dump (first 32 bytes):
38 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 8...............
00 00 01 00 03 00 00 00 43 10 01 00 00 00 00 00 ........C.......
backtrace:
[<ffffffff814e9d55>] kmemleak_alloc+0x25/0x60
[<ffffffff811198fb>] __kmalloc_node_track_caller+0x1ab/0x220
[<ffffffff8141dc9b>] __alloc_skb+0x7b/0x180
[<ffffffff814ddb82>] wireless_send_event+0x1f2/0x410
[<ffffffffa01b7084>] ___cfg80211_scan_done+0xe4/0x110 [cfg80211]
[<ffffffffa01b70d6>] __cfg80211_scan_done+0x26/0x50 [cfg80211]
[<ffffffff8106de80>] worker_thread+0x1d0/0x380
[<ffffffff81073266>] kthread+0xa6/0xb0
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
Luis
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree
2009-09-04 22:15 kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree Luis R. Rodriguez
@ 2009-09-04 22:32 ` Catalin Marinas
2009-09-04 22:40 ` Luis R. Rodriguez
2009-09-05 9:27 ` Johannes Berg
1 sibling, 1 reply; 5+ messages in thread
From: Catalin Marinas @ 2009-09-04 22:32 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless
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
> [<ffffffffa01b7084>] ___cfg80211_scan_done+0xe4/0x110 [cfg80211]
> [<ffffffffa01b70d6>] __cfg80211_scan_done+0x26/0x50 [cfg80211]
> [<ffffffff8106de80>] worker_thread+0x1d0/0x380
> [<ffffffff81073266>] kthread+0xa6/0xb0
> [<ffffffff810130ca>] child_rip+0xa/0x20
> [<ffffffffffffffff>] 0xffffffffffffffff
If you force a few scans, do we still get the same objects reported as
leaks?
> unreferenced object 0xffff8800322bd000 (size 4096):
> comm "events/1", pid 10, jiffies 4295050369
> hex dump (first 32 bytes):
> 38 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 8...............
> 00 00 01 00 03 00 00 00 43 10 01 00 00 00 00 00 ........C.......
> backtrace:
> [<ffffffff814e9d55>] kmemleak_alloc+0x25/0x60
> [<ffffffff811198fb>] __kmalloc_node_track_caller+0x1ab/0x220
> [<ffffffff8141dc9b>] __alloc_skb+0x7b/0x180
> [<ffffffff814ddb82>] wireless_send_event+0x1f2/0x410
> [<ffffffffa01b7084>] ___cfg80211_scan_done+0xe4/0x110 [cfg80211]
> [<ffffffffa01b70d6>] __cfg80211_scan_done+0x26/0x50 [cfg80211]
> [<ffffffff8106de80>] worker_thread+0x1d0/0x380
> [<ffffffff81073266>] kthread+0xa6/0xb0
> [<ffffffff810130ca>] child_rip+0xa/0x20
> [<ffffffffffffffff>] 0xffffffffffffffff
This is probably referenced from the first one, so we usually need to
look into the first reported leak.
--
Catalin
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree
2009-09-04 22:32 ` Catalin Marinas
@ 2009-09-04 22:40 ` Luis R. Rodriguez
0 siblings, 0 replies; 5+ messages in thread
From: Luis R. Rodriguez @ 2009-09-04 22:40 UTC (permalink / raw)
To: Catalin Marinas; +Cc: linux-wireless
On Fri, Sep 4, 2009 at 3:32 PM, Catalin Marinas<catalin.marinas@arm.com> 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
>> [<ffffffffa01b7084>] ___cfg80211_scan_done+0xe4/0x110 [cfg80211]
>> [<ffffffffa01b70d6>] __cfg80211_scan_done+0x26/0x50 [cfg80211]
>> [<ffffffff8106de80>] worker_thread+0x1d0/0x380
>> [<ffffffff81073266>] kthread+0xa6/0xb0
>> [<ffffffff810130ca>] child_rip+0xa/0x20
>> [<ffffffffffffffff>] 0xffffffffffffffff
>
> If you force a few scans, do we still get the same objects reported as
> leaks?
Just tried it, and yes.
Luis
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree
2009-09-04 22:15 kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree Luis R. Rodriguez
2009-09-04 22:32 ` Catalin Marinas
@ 2009-09-05 9:27 ` Johannes Berg
2009-09-05 19:36 ` Luis R. Rodriguez
1 sibling, 1 reply; 5+ messages in thread
From: Johannes Berg @ 2009-09-05 9:27 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless, Catalin Marinas
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
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? And if you do, can you figure out whether
this is "skb" or "compskb"?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree
2009-09-05 9:27 ` Johannes Berg
@ 2009-09-05 19:36 ` Luis R. Rodriguez
0 siblings, 0 replies; 5+ messages in thread
From: Luis R. Rodriguez @ 2009-09-05 19:36 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless, Catalin Marinas
On Sat, Sep 5, 2009 at 2:27 AM, Johannes Berg<johannes@sipsolutions.net> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-09-05 19:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-04 22:15 kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree Luis R. Rodriguez
2009-09-04 22:32 ` Catalin Marinas
2009-09-04 22:40 ` Luis R. Rodriguez
2009-09-05 9:27 ` Johannes Berg
2009-09-05 19:36 ` Luis R. Rodriguez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox