public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Pablo Martin-Gomez <pmartin-gomez@freebox.fr>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 0/7] Do not read band-dependent reserved bits
Date: Wed, 15 Apr 2026 15:38:42 -0700	[thread overview]
Message-ID: <4e3266fa-d9cd-40ef-b60a-985ef2170224@oss.qualcomm.com> (raw)
In-Reply-To: <20260410190354.394742-1-pmartin-gomez@freebox.fr>

On 4/10/2026 12:03 PM, Pablo Martin-Gomez wrote:
> This series is a recyclying and extension of a previous attempt [1] to 
> not read reserved bits depending on the current band for HE/EHT STAs.
> 
> Convention (section 9.2.2 of 802.11-2024) states that reserved bits
> should be set to 0 (unless stated otherwise) and not to be read. Some
> STAs do not respect the convention in transmission and the kernel do not
> respect the convention in reception. The practical effect can be a
> really low throughtput between a MT7927 Windows STA and a ath12k Linux AP.
> 
> I've been quite drastic and added a check of the current band before
> read a bit that might be reserved whatever it's from an IE that was
> received or an IE will be sent. I also removed checks where they didn't
> make much sense and the current band was complicated/impossible to
> retrieve. That is why I'm positing this as a RFC.
> 
> [1]: https://lore.kernel.org/linux-wireless/20250120114551.1542812-1-pmartin-gomez@freebox.fr/
> 
> 
> Pablo Martin-Gomez (7):
>   wifi: nl80211: remove EHT IE size validation
>   wifi: make EHT capa size check not read reserved bits
>   wifi: make HE capa size check not read reserved bits
>   wifi: do not read band-dependent reserved bits
>   wifi: ath11k: do not read band-dependent reserved bits
>   wifi: ath12k: do not read band-dependent reserved bits
>   wifi: mt76: do not read band-dependent reserved bits
> 
>  drivers/net/wireless/ath/ath11k/mac.c         | 11 +--
>  drivers/net/wireless/ath/ath12k/mac.c         | 35 +++++----
>  .../net/wireless/mediatek/mt76/mt7996/mcu.c   | 16 ++--
>  include/linux/ieee80211-eht.h                 | 58 +++++++++------
>  include/linux/ieee80211-he.h                  | 21 +++---
>  net/mac80211/debugfs_sta.c                    |  7 +-
>  net/mac80211/eht.c                            |  3 +-
>  net/mac80211/he.c                             | 73 ++++++++++---------
>  net/mac80211/mlme.c                           |  7 +-
>  net/mac80211/util.c                           | 12 +--
>  net/mac80211/vht.c                            |  2 +-
>  net/wireless/nl80211.c                        | 31 +++-----
>  12 files changed, 149 insertions(+), 127 deletions(-)
> 

Please use scripts/get_maintainer.pl to identify all necessary recipients for
your patches. Or start using 'b4' which does all the work for you. You are
modifying drivers without including the per-driver mailing lists and maintainers.

/jeff

      parent reply	other threads:[~2026-04-15 22:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 19:03 [RFC PATCH 0/7] Do not read band-dependent reserved bits Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 1/7] wifi: nl80211: remove EHT IE size validation Pablo Martin-Gomez
2026-04-10 20:25   ` Johannes Berg
2026-04-10 19:03 ` [RFC PATCH 2/7] wifi: make EHT capa size check not read reserved bits Pablo Martin-Gomez
2026-04-10 20:35   ` Johannes Berg
2026-04-10 19:03 ` [RFC PATCH 3/7] wifi: make HE " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 4/7] wifi: do not read band-dependent " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 5/7] wifi: ath11k: " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 6/7] wifi: ath12k: " Pablo Martin-Gomez
2026-04-10 19:03 ` [RFC PATCH 7/7] wifi: mt76: " Pablo Martin-Gomez
2026-04-15 22:38 ` Jeff Johnson [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=4e3266fa-d9cd-40ef-b60a-985ef2170224@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pmartin-gomez@freebox.fr \
    /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