From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH wireless-2.6] mac80211: delete AddBA response timer
Date: Tue, 05 Oct 2010 13:36:09 -0700 [thread overview]
Message-ID: <4CAB8C39.5090201@candelatech.com> (raw)
In-Reply-To: <1286309408.3641.31.camel@jlt3.sipsolutions.net>
On 10/05/2010 01:10 PM, Johannes Berg wrote:
> On Tue, 2010-10-05 at 21:40 +0200, Johannes Berg wrote:
>> From: Johannes Berg<johannes.berg@intel.com>
>>
>> We never delete the addBA response timer, which
>> is typically fine, but if the station it belongs
>> to is deleted very quickly after starting the BA
>> session, before the peer had a chance to reply,
>> the timer may fire after the station struct has
>> been freed already. Therefore, we need to delete
>> the timer in a suitable spot -- best when the
>> session is being stopped (which will happen even
>> then) in which case the delete will be a no-op
>> most of the time.
>>
>> I've reproduced the scenario and tested the fix.
>
> Ok, can you add:
>
> This fixes the crash reported at
> http://mid.gmane.org/4CAB6F96.6090701@candelatech.com
I can no longer reproduce that problem, so it looks fixed
to me.
The data corruption issue still exists, however...
Thanks!
Ben
>
> to the changelog?
>
> johannes
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-10-05 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:40 [PATCH wireless-2.6] mac80211: delete AddBA response timer Johannes Berg
2010-10-05 20:10 ` Johannes Berg
2010-10-05 20:36 ` Ben Greear [this message]
2010-10-05 20:41 ` Johannes Berg
2010-10-05 20:52 ` Ben Greear
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=4CAB8C39.5090201@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).