From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: kmemleak report in 3.9.5+, related to cfg80211_inform_bss_frame
Date: Sat, 15 Jun 2013 19:11:15 +0200 [thread overview]
Message-ID: <1371316275.8319.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51BB9DC5.2020509@candelatech.com> (sfid-20130615_004841_632650_1CE63E73)
On Fri, 2013-06-14 at 15:48 -0700, Ben Greear wrote:
> I've instrumented all (as far as I can tell) allocation points
> and destruction points for the ies, and I am keeping a separate
> list of structures to record some info about each ies.
>
> I loaded up lots of stations, let them bounce around for a while,
> and then did an 'rmmod ath9k'.
>
> I still see 14 ies entries in my debug list. Should
> I expect to see zero ies data structures left after
> I rmmod all wifi drivers, or is it normal for a few
> to be left around?
No, that's decidedly not normal, but that's pretty much just what
kmemleak already told us, no? Good to verify, but doesn't really help
pinpoint the problem either, I'd say :-(
johannes
next prev parent reply other threads:[~2013-06-15 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 19:00 kmemleak report in 3.9.5+, related to cfg80211_inform_bss_frame Ben Greear
2013-06-11 19:08 ` Ben Greear
2013-06-12 0:36 ` Ben Greear
2013-06-14 22:48 ` Ben Greear
2013-06-15 17:11 ` Johannes Berg [this message]
2013-06-15 19:18 ` Ben Greear
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=1371316275.8319.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.