From: Jouni Malinen <j@w1.fi>
To: "Luis R. Rodriguez" <lrodriguez@Atheros.com>
Cc: linville@tuxdriver.com, stable@kernel.org,
linux-wireless@vger.kernel.org, Paul Stewart <pstew@google.com>,
Amod Bodas <amod.bodas@Atheros.com>,
Johannes Berg <johannes@sipsolutions.net>,
Vasanthakumar Thiagarajan <vasanth@Atheros.com>
Subject: Re: [PATCH] mac80211: fix rate_control_send_low warnings for delbas
Date: Tue, 28 Sep 2010 16:02:11 -0700 [thread overview]
Message-ID: <20100928230211.GA9844@jm.kir.nu> (raw)
In-Reply-To: <20100928222945.GB10932@tux>
On Tue, Sep 28, 2010 at 03:29:45PM -0700, Luis R. Rodriguez wrote:
> Added support for cfg80211/mac80211 to cleanly roam between two BSSes
> on an ESS by allowing the station to reassociate to an old AP and
> only when that is done drop the old association. What we forgot to
> take into consideration is that when we disassociate with the older
> AP we may need to transmit frames to that AP and those frames may
> actually be intended to go under a different channel and even sometimes
> a completely separate band than the new APs.
which frames are you talking about here? When reassociating to a new BSS
in an ESS, there should be no need to transmit frames to the old AP
anymore, i.e., we are never associated with more than one BSS (when
talking about a single vif). We could just drop any potential TX frame
to the old AP after the moment the new AP is marked associated.
> + * @channel: the channel this sta belongs to
> struct ieee80211_sta {
> + struct ieee80211_channel *channel;
> u32 supp_rates[IEEE80211_NUM_BANDS];
> u8 addr[ETH_ALEN];
> u16 aid;
> diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
> @@ -1213,6 +1217,12 @@ ieee80211_tx_prepare(struct ieee80211_sub_if_data *sdata,
> if (!tx->sta)
> tx->sta = sta_info_get(sdata, hdr->addr1);
>
> + if (tx->sta && tx->sta->sta.channel &&
> + tx->sta->sta.channel->center_freq != tx->channel->center_freq) {
> + I802_DEBUG_INC(local->tx_handlers_drop_wrong_channel);
> + return TX_DROP;
> + }
Could this drop some off-channel frames should we happen to have a STA
entry for the destination? I'm not sure about all implications of this,
but I could not convince myself that this would be safe for all P2P use
cases (e.g., frame exchange on non-operating channel with a device that
happens to be in group with us).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2010-09-28 23:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 22:29 [PATCH] mac80211: fix rate_control_send_low warnings for delbas Luis R. Rodriguez
2010-09-28 23:02 ` Jouni Malinen [this message]
2010-09-28 23:58 ` Luis R. Rodriguez
2010-09-29 5:20 ` Vasanthakumar Thiagarajan
2010-09-29 7:24 ` Luis R. Rodriguez
2010-09-29 8:56 ` Vasanthakumar Thiagarajan
2010-09-29 17:16 ` Luis R. Rodriguez
2010-09-29 17:24 ` Johannes Berg
2010-09-29 8:18 ` Johannes Berg
2010-09-29 17:10 ` Luis R. Rodriguez
2010-09-29 17:25 ` Johannes Berg
2010-09-30 17:53 ` Luis R. Rodriguez
2010-10-01 20:07 ` 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=20100928230211.GA9844@jm.kir.nu \
--to=j@w1.fi \
--cc=amod.bodas@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@Atheros.com \
--cc=pstew@google.com \
--cc=stable@kernel.org \
--cc=vasanth@Atheros.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;
as well as URLs for NNTP newsgroup(s).