From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Ron Rindjunksi <ron.rindjunski@intel.com>
Subject: Re: iwlwifi workaround for mac80211 sequence number bug
Date: Thu, 10 Jul 2008 00:24:51 +0200 [thread overview]
Message-ID: <1215642292.3246.79.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240807091517y40f6ab8cscc352bfdaa0d715@mail.gmail.com> (sfid-20080710_001755_843107_650682D8)
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Thu, 2008-07-10 at 01:17 +0300, Tomas Winkler wrote:
> This is not a bug in mac.
> The sequence number can be committed only if the packet is not dropped
> somewhere in the driver. See lower in the function.. There are plenty
> of places on the TX path when packet can be dropped this it's last
> station. There is no reason to pushing this into mac
I don't see it that way. In fact, in the code I'm looking at, there is
nothing that drops the frame before committing the sequence number
change after assigning it.
And all the cases where it drops the frame _before_ the piece of code I
quoted don't actually matter, the first bunch of those are bugs and the
not associated one is strange but most likely doesn't matter either (if
we're not associated sequence numbers don't matter), and the
"destination STA entry not found" one doesn't matter either since that
means there's some disconnect/bug between iwlwifi and mac80211 since
they should synchronise via sta_notify().
Which particular item do you see as problematic?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-07-09 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 22:11 iwlwifi workaround for mac80211 sequence number bug Johannes Berg
2008-07-09 22:17 ` Tomas Winkler
2008-07-09 22:24 ` Johannes Berg [this message]
2008-07-09 22:45 ` Tomas Winkler
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=1215642292.3246.79.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ron.rindjunski@intel.com \
--cc=tomasw@gmail.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