From: Johannes Berg <johannes@sipsolutions.net>
To: Ron Rindjunsky <ron.rindjunsky@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Winkler, Tomas" <tomas.winkler@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211: holding sta_info for non associated stations
Date: Tue, 01 Apr 2008 14:28:16 +0200 [thread overview]
Message-ID: <1207052896.5143.76.camel@johannes.berg> (raw)
In-Reply-To: <c85cb4470803310746h36b20d0egce98f8cea3becb0b@mail.gmail.com> (sfid-20080331_154705_823745_A1E01497)
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Hi,
> If i associate to a random AP "x" (what happened automatically as i
> was configured by ifup scripts to do that), and then scan and
> associate to my desired AP "y", i notice that AP "x" was not removed
> from the mac80211 station table. Then, what happened was that during
> ieee80211_stop, when we reach
>
> list_for_each_entry_rcu(sta, &local->sta_list, list) {
> if (sta->sdata == sdata)
> ieee80211_sta_tear_down_BA_sessions(dev, sta->addr);
> }
>
> we try to tear down sessions to irrelevant stations (AP "x" in my
> example), which leads to bugs.
Why would that lead to bugs? That station was known, and there are no
sessions for that AP.
> did i miss something, or is there really a problem in the state
> machine in the described scenario?
There might be a problem in that we forget to remove that AP under some
circumstances but it shouldn't matter, we always can have multiple
stations in our table.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-04-01 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 14:46 mac80211: holding sta_info for non associated stations Ron Rindjunsky
2008-04-01 12:28 ` Johannes Berg [this message]
2008-04-01 21:19 ` Tomas Winkler
2008-04-02 9:08 ` Johannes Berg
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=1207052896.5143.76.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ron.rindjunsky@intel.com \
--cc=tomas.winkler@intel.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