From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linville@tuxdriver.com, johannes@sipsolutions.net, j@w1.fi
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [PATCH 0/3] ath9k: rate fix for invalid frames
Date: Tue, 9 Jun 2009 04:30:08 -0400 [thread overview]
Message-ID: <1244536211-22535-1-git-send-email-lrodriguez@atheros.com> (raw)
We've tried a few things to find the real root cause to
the ath9k rate control assert. This is it, turns out we
make some assumptions about scanning and nullfunc frames.
We fix those assumptions here.
I'll send the ath9k rate control cleanup stuff later
though, all of that is still valid.
I think the iwlwifi rate control work arounds could be removed
now though but not sure, I saw in the bug report the get_rate
warn on was found during disassoc or something like that which
I cannot see being triggerable by the conditions found in these
patches unless iwlwifi is getting frames through some other
uknown mean.
Luis R. Rodriguez (3):
mac80211: fix - drop frames for sta with no valid rate
mac80211: add debugfs counter for not valid birate frames
ath9k: downgrade assert in rc.c for invalid rate
drivers/net/wireless/ath/ath9k/rc.c | 16 ++++++++++---
include/net/mac80211.h | 11 +++++++++
net/mac80211/debugfs.c | 4 +++
net/mac80211/ieee80211_i.h | 2 +
net/mac80211/tx.c | 39 +++++++++++++++++++++++++++++++++++
5 files changed, 68 insertions(+), 4 deletions(-)
next reply other threads:[~2009-06-09 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 8:30 Luis R. Rodriguez [this message]
2009-06-09 8:30 ` [PATCH 1/3] mac80211: fix - drop frames for sta with no valid rate Luis R. Rodriguez
2009-06-09 8:54 ` Johannes Berg
2009-06-09 8:55 ` Luis R. Rodriguez
2009-06-09 8:30 ` [PATCH 2/3] mac80211: add debugfs counter for not valid birate frames Luis R. Rodriguez
2009-06-09 8:30 ` [PATCH 3/3] ath9k: downgrade assert in rc.c for invalid rate 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=1244536211-22535-1-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=j@w1.fi \
--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