Linux wireless drivers development
 help / color / mirror / Atom feed
From: Thomas Pedersen <thomas@adapt-ip.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: process S1G Operation element before HT
Date: Tue, 29 Sep 2020 11:44:14 -0700	[thread overview]
Message-ID: <8e9418eff4fce082312af7ca9a81bc04@adapt-ip.com> (raw)
In-Reply-To: <8cb48d6d229aa1d01f815c3a2336799b780b510d.camel@sipsolutions.net>

On 2020-09-29 11:32, Johannes Berg wrote:
> On Tue, 2020-09-29 at 11:19 -0700, Thomas Pedersen wrote:
>> The sband->ht_cap was being processed before S1G Operation
>> element.  Since the HT capability element should not be
>> present on the S1G band, avoid processing potential
>> garbage by moving the call to
>> ieee80211_apply_htcap_overrides() to after the S1G block.
> 
> Ah, heh. I hadn't even realized that.
> 
> What I meant though was something else: we have
> 
>         if (s1g_oper && sband->band == NL80211_BAND_S1GHZ) {
> 		...
> 		goto out;
> 	}
> 
> 	// process ht cap overrides (after this patch)
> 
> 	// check HT oper
> 
> 	// check VHT oper
> 
> 	// ...
> 
> So given that first condition, if you actually have an S1G AP *without*
> S1G operation element (for some reason), you'd start processing HT, 
> VHT,
> and whatever else capabilities, sending us down a misleading and likely
> very confusing path, which seems like it should be avoided?

Ah ok, yes the !s1g_oper case. I'll take a look.

-- 
thomas

      reply	other threads:[~2020-09-29 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 18:19 [PATCH] mac80211: process S1G Operation element before HT Thomas Pedersen
2020-09-29 18:32 ` Johannes Berg
2020-09-29 18:44   ` Thomas Pedersen [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=8e9418eff4fce082312af7ca9a81bc04@adapt-ip.com \
    --to=thomas@adapt-ip.com \
    --cc=johannes@sipsolutions.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox