From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: Bob Copeland <me@bobcopeland.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Jouni.Malinen@Atheros.com
Subject: Re: [PATCH] mac80211: Tear down aggregation sessions for suspend/resume
Date: Mon, 16 Mar 2009 08:15:28 +0100 [thread overview]
Message-ID: <1237187728.27769.2.camel@johannes.local> (raw)
In-Reply-To: <18877.56125.181203.703218@gargle.gargle.HOWL>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On Mon, 2009-03-16 at 10:23 +0530, Sujith wrote:
> > I think the deadlock went away, not sure what fixed it but I guess
> > the HT rework. I tested it a couple of weeks ago on ath5k and Luis
> > did on ath9k so I say let's go ahead and apply the patch... in the
> > meantime I'll try again on ath5k just to be sure.
Ok.
> There is a window for a race. Something like this:
>
> From mac80211:
>
> __ieee80211_suspend()
> tear_down_BA_sessions(TX, RX)
> ampdu_action(STOP)
> remove_vifs()
>
> At this point, the driver executes its remove_interface routine.
> While we are doing this, a TX completion interrupt could be raised,
> (HW hasn't been stopped yet) and nothing stops the driver from calling
> ieee80211_start_tx_ba_session().
>
> So the question is: should mac80211 deny ADDBA requests in this case ?
Interesting observation. We probably should indeed reject that, and also
if the peer asks for sending aggregation again right away like some
Broadcom APs will.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-16 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 6:43 [PATCH] mac80211: Tear down aggregation sessions for suspend/resume Sujith
2009-03-15 18:02 ` Johannes Berg
2009-03-15 18:48 ` Sujith
2009-03-16 1:28 ` Bob Copeland
2009-03-16 4:53 ` Sujith
2009-03-16 7:15 ` Johannes Berg [this message]
2009-03-16 7:39 ` Sujith
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=1237187728.27769.2.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Jouni.Malinen@Atheros.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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