From: bruno randolf <br1@einfach.org>
To: Vladimir Koutny <vlado@work.ksp.sk>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: eliminate IBSS warning in rate_lowest_index()
Date: Sat, 14 Jun 2008 20:41:04 +0200 [thread overview]
Message-ID: <200806142041.04146.br1@einfach.org> (raw)
In-Reply-To: <48528944.2040907@work.ksp.sk>
On Friday 13 June 2008 16:50:44 Vladimir Koutny wrote:
> In IBSS mode prior to join/creation of new IBSS it is possible that
> a frame from unknown station is received and an ibss_add_sta() is
> called. This will cause a warning in rate_lowest_index() since the
> list of supported rates of our station is not initialized yet.
>
> The fix is to add ibss stations with a rate we received that frame
> at; this single-element set will be extended later based on beacon
> data. Also there is no need to store stations from a foreign IBSS.
makes sense.
Acked-by: Bruno Randolf <br1@einfach.org>
> - sta->supp_rates[local->hw.conf.channel->band] =
> - sdata->u.sta.supp_rates_bits[local->hw.conf.channel->band];
> + if (supp_rates)
> + sta->supp_rates[band] = supp_rates;
> + else
> + sta->supp_rates[band] = sdata->u.sta.supp_rates_bits[band];
i'm not sure about that last line. i know, it was like that before - but i
think we shouldn't assume another station supports the same rates as we do in
any case. we normally get the supported rates of another station thru the
beacons we receive. or from received data packets (thanks to this patch).
bruno
prev parent reply other threads:[~2008-06-18 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 14:50 [PATCH] mac80211: eliminate IBSS warning in rate_lowest_index() Vladimir Koutny
2008-06-13 14:54 ` Johannes Berg
2008-06-14 18:41 ` bruno randolf [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=200806142041.04146.br1@einfach.org \
--to=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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;
as well as URLs for NNTP newsgroup(s).