From: Karl Beldan <karl.beldan@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Karl Beldan <karl.beldan@rivierawaves.com>
Subject: Re: [PATCH] mac80211/trivial: fix typo in starting baserate for rts_cts_rate_idx
Date: Thu, 9 Oct 2014 22:56:22 +0200 [thread overview]
Message-ID: <20141009205622.GC19745@gobelin> (raw)
In-Reply-To: <1412868141.1828.57.camel@jlt4.sipsolutions.net>
On Thu, Oct 09, 2014 at 05:22:21PM +0200, Johannes Berg wrote:
> On Thu, 2014-10-09 at 16:45 +0200, Karl Beldan wrote:
>
> > > > The typo is clearly showing but the faulty behavior clearly demands more
> > > > detail indeed.
> > > >
> > > > It affects non-(V)HT rates and can lead to selecting an rts_cts rate
> > > > that is not a basic rate or way superior to the reference rate (ATM
> > > > rates[0] used for the 1st attempt of the protected frame data).
> > > > E.g, assuming the drivers register growing (bitrate) sorted
> > > > ieee80211_rate tables, having :
> > > > - rates[0].idx == d'2 and basic_rates == b'10100
> > > > will select rts_cts idx b'10011 & ~d'(BIT(2)-1), i.e. 1, likewise
> > > > - rates[0].idx == d'2 and basic_rates == b'10001
> > > > will select rts_cts idx b'10000
> > > > The first is not a basic rate and the second is > rates[0].
> > > >
> > > > I hope it clarifies things enough.
> > >
> > > Well, I'm still not sure which tree I should put it in, I guess?
> > >
> >
> > All I can say is that nor this faulty behavior nor the correspond fix
> > are likely to cause a crash (we always tx registered rates).
>
> But it's still pretty misbehaving, no? That IMHO warrants fixing and
> even cc stable.
>
Also, for the record, ATM we have only one rts_cts rate. A way to handle
every retry rates is still missing, along with (V)HT rates.
Karl
prev parent reply other threads:[~2014-10-09 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 13:53 [PATCH] mac80211/trivial: fix typo in starting baserate for rts_cts_rate_idx Karl Beldan
2014-10-09 9:06 ` Johannes Berg
2014-10-09 14:06 ` Karl Beldan
2014-10-09 14:15 ` Johannes Berg
2014-10-09 14:45 ` Karl Beldan
2014-10-09 15:22 ` Johannes Berg
2014-10-09 16:28 ` Karl Beldan
2014-10-09 18:35 ` Johannes Berg
2014-10-09 20:56 ` Karl Beldan [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=20141009205622.GC19745@gobelin \
--to=karl.beldan@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=karl.beldan@rivierawaves.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.