From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: kmemleak reports on wireless-testing master-2009-09-04 + kmemleak tree
Date: Sat, 05 Sep 2009 11:27:01 +0200 [thread overview]
Message-ID: <1252142821.1175.10.camel@johannes.local> (raw)
In-Reply-To: <43e72e890909041515s38e7c502kf552a5cf90e99d94@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2009-09-05 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-09-05 19:36 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1252142821.1175.10.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=catalin.marinas@arm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox