From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Zhu Yi <yi.zhu@intel.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: delete addba_resp_timer when stop Tx BA session
Date: Mon, 28 Dec 2009 08:10:10 -0800 [thread overview]
Message-ID: <43e72e890912280810o6a2d3f9dye562c75061e1f486@mail.gmail.com> (raw)
In-Reply-To: <1261988312.22470.5.camel@johannes.local>
On Mon, Dec 28, 2009 at 12:18 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2009-12-28 at 11:18 +0800, Zhu Yi wrote:
>> We start an one shot addba_resp_timer in ieee80211_start_tx_ba_session
>> but don't delete it in __ieee80211_stop_tx_ba_session. This will cause
>> problem in suspend and resume. When suspend happens without the timer
>> deleted, the timer handler will be called immediately after resume and
>> messes up driver status.
>>
>> See http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2134
>> comment #22 for more details.
>
> Hmm. The timer checks
>
> if ((*state & (HT_ADDBA_REQUESTED_MSK | HT_ADDBA_RECEIVED_MSK)) !=
> HT_ADDBA_REQUESTED_MSK) {
>
> which /should/ make it a no-op in the case you mention because we tear
> down sessions, or does that not reset their state properly?
>
> Ok, so ___ieee80211_stop_tx_ba_session() doesn't, in fact, clear the
> mask right away, so I think we should add HT_AGG_STATE_REQ_STOP_BA_MSK
> to the code I quoted above?
When the patch addresses the above can you cc stable if applicable.
> In any case the del_timer_sync isn't right there and we also shouldn't
> really use it (per Linus)
Why is that?
Luis
prev parent reply other threads:[~2009-12-28 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 3:18 [PATCH] mac80211: delete addba_resp_timer when stop Tx BA session Zhu Yi
2009-12-28 8:18 ` Johannes Berg
2009-12-28 16:10 ` Luis R. Rodriguez [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=43e72e890912280810o6a2d3f9dye562c75061e1f486@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@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