From: bruno randolf <bruno@thinktube.com>
To: Vladimir Koutny <vlado@work.ksp.sk>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC] WARNING: at net/mac80211/ieee80211_rate.h:159 rate_lowest_index()
Date: Tue, 29 Apr 2008 20:42:20 +0200 [thread overview]
Message-ID: <200804292042.20500.bruno@thinktube.com> (raw)
In-Reply-To: <48174652.6080909@work.ksp.sk>
On Tuesday 29 April 2008 18:01:22 Vladimir Koutny wrote:
> Hi,
> the warning in $subj can pop up in the following scenario:
>
> - iwconfig wlan0 mode ad-hoc; ifconfig wlan0 up
> - a frame arrives from an unknown station which triggers
> ieee80211_ibss_sta_add() (called from prepare_for_handlers())
yep, i have seen this warning too, just didn't get around to look into it...
> In this case, we create a new sta entry, fill in supp_rates field,
> initialize rate_control algo, and insert this sta entry into the list.
>
> The problem is the assignment for supp_rates:
>
> sta->supp_rates[local->hw.conf.channel->band] =
> sdata->u.sta.supp_rates_bits[local->hw.conf.channel->band];
>
> because sdata->u.sta.supp_rates_bits is set only when we actually
> join an ibss, which is not the case in this scenario; so we assign
> zero here. Then, the code in rate_control_pid_rate_init() calls
> rate_lowest_index() for some reason, and since no supported rate is
> found, this warning is issued.
>
>
> The question is how sta->supp_rates should be initialized:
>
> - we could initialize it to our sta's rates, but then we could
> probably transmit to a station at unsupported rate
isn't this what is done right now, and the rateset is zero sometimes and then
we get the warning?
this might be wrong anyways: as you said it could make us send frames at an
unsupported rate.
> - add new ibss station only on received beacon, not on a data frame;
> currently, beacons are ignored for this purpose (they just update
> the bss list later on)
i think stations should be added on reception of both beacons and data frames.
> - something else (like 1Mbps only)?
what about the rate of the currently received data frame (and maybe any other
rates we could safely deduce from that)?
bruno
next prev parent reply other threads:[~2008-04-29 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 16:01 [RFC] WARNING: at net/mac80211/ieee80211_rate.h:159 rate_lowest_index() Vladimir Koutny
2008-04-29 18:42 ` bruno randolf [this message]
2008-04-30 15:03 ` Vladimir Koutny
2008-04-30 15:05 ` Johannes Berg
2008-04-30 15:46 ` Vladimir Koutny
2008-04-30 14:20 ` Johannes Berg
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=200804292042.20500.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vlado@work.ksp.sk \
/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