From: Greg KH <gregkh@linuxfoundation.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: stable@vger.kernel.org, miriam.rachel.korenblit@intel.com,
johannes.berg@intel.com, quic_ramess@quicinc.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: stable backport: wifi: mac80211: track capability/opmode NSS separately
Date: Mon, 29 Jul 2024 12:49:11 +0200 [thread overview]
Message-ID: <2024072900-persevere-lecturer-b749@gregkh> (raw)
In-Reply-To: <6d402141-a457-4096-a487-56b4140361be@hauke-m.de>
On Sat, Jul 27, 2024 at 12:54:21AM +0200, Hauke Mehrtens wrote:
> Hi,
>
> Please backport the following patch back to the stable series 6.6 and 6.1:
> commit a8bca3e9371dc5e276af4168be099b2a05554c2a
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Wed Feb 28 12:01:57 2024 +0100
>
> wifi: mac80211: track capability/opmode NSS separately
>
> There is a small conflict in the copyright year update in
> net/mac80211/sta_info.h, just take the 2024 version.
>
>
> On kernel 6.1 please backport this patch first to make the other one apply:
> commit 57b341e9ab13e5688491bfd54f8b5502416c8905
> Author: Rameshkumar Sundaram <quic_ramess@quicinc.com>
> Date: Tue Feb 7 17:11:46 2023 +0530
>
> wifi: mac80211: Allow NSS change only up to capability
>
>
>
> This commit fixes a throughput regression introduced into Linux stable with
> the backport of following commit:
>
> commit dd6c064cfc3fc18d871107c6f5db8837e88572e4
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Mon Jan 29 15:53:55 2024 +0100
>
> wifi: mac80211: set station RX-NSS on reconfig
>
> On older kernel versions it is harder to backport the fixes, maybe revert
> the offending commit in Linux stable 5.15 and older.
>
> This regression was found by multiple users of OpenWrt in Wifi AP mode.
> See the discussion in this forum thread:
> https://forum.openwrt.org/t/openwrt-23-05-4-service-release/204514/111
>
> Thank you KONG from the OpenWrt forum for finding the commit which reduced
> the Wifi throughput.
This is a bit complex, please provide a series of backported patches for
each tree that you have tested and done the needed changes to get
working properly. Otherwise, the above descriptions are going to take a
long time for us to get to, sorry, as we have much more "simpler" things
to backport at this point in time.
thanks,
greg k-h
prev parent reply other threads:[~2024-07-29 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 22:54 stable backport: wifi: mac80211: track capability/opmode NSS separately Hauke Mehrtens
2024-07-29 10:49 ` Greg KH [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=2024072900-persevere-lecturer-b749@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=netdev@vger.kernel.org \
--cc=quic_ramess@quicinc.com \
--cc=stable@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