From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Lots of confusion on bss refcounting.
Date: Tue, 18 Jun 2013 14:36:24 -0700 [thread overview]
Message-ID: <51C0D2D8.3080207@candelatech.com> (raw)
In-Reply-To: <1371570723.22256.0.camel@jlt4.sipsolutions.net>
On 06/18/2013 08:52 AM, Johannes Berg wrote:
>
>>> You mean ->current_bss? That should be handled in all the callbacks in
>>> sme.c or so
>>
>> Looks like much of the action happens on work-queues. I'm wondering if
>> we managed to delete wdev objects before we have completely cleaned up
>> in some cases...
>
> Don't we flush work structs appropriately?
I'm still seeing leaks after all those patches I posted...so I'm still
looking. The leaked bss objects have a quite large refcount, in the
hundreds after an hour or so of running, so this is probably more than
a strange race somewhere.
This code looks questionable in wireless/mlme.c
int __cfg80211_mlme_assoc()
.....
It grabs a reference using cfg80211_get_bss, but it only
does a put on the reference if there was an error code.
The __cfg80211_mlme_auth a bit above always does a put on
the reference.
I'm thinking mlme_assoc should also always do put. Any
reason you can think of otherwise?
Thanks,
Ben
>
> johannes
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-06-18 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 18:49 Lots of confusion on bss refcounting Ben Greear
2013-06-17 19:02 ` Johannes Berg
2013-06-17 19:09 ` Ben Greear
2013-06-17 21:31 ` Ben Greear
2013-06-18 0:30 ` Ben Greear
2013-06-18 12:49 ` Johannes Berg
2013-06-18 15:47 ` Ben Greear
2013-06-18 15:52 ` Johannes Berg
2013-06-18 15:59 ` Ben Greear
2013-06-18 21:36 ` Ben Greear [this message]
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=51C0D2D8.3080207@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).