public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: LB F <goainwo@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next] wifi: rtw88: validate RX rate to prevent out-of-bound
Date: Tue, 24 Mar 2026 01:07:05 +0000	[thread overview]
Message-ID: <27c838b55d794708b875fef31758ae8e@realtek.com> (raw)
In-Reply-To: <CALdGYqS_ROWrsYishahHxEthwYYfxurOxCCWJjOApgbnmekeWw@mail.gmail.com>

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > The reported RX rate might be unexpected, causing kernel warns:
> >   Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
> >   WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x183/0x1020
> [mac80211]
> > As the RX rate can be index of an array under certain conditions, validate
> > it to prevent accessing array out-of-bound potentially.
> 
> Tested on HP Notebook P3S95EA#ACB (kernel 6.19.9-1-cachyos):
> 
>   - No WARNING: net/mac80211/rx.c:5491 observed after patch.
>   - System remains fully stable through idle, load, Bluetooth A2DP
>     usage, and multiple suspend/resume cycles.
>   - Zero h2c or lps errors in dmesg.
> 
> Tested-by: Oleksandr Havrylov <goainwo@gmail.com>

Thanks for your test. As the change in data path, I'd add an unlikely()
by v2. Also, take your test info. If v2 doesn't work to you (I think
the result of v2 must be identical to v1), please NACK me by v2 patch
I will send out right away.

Ping-Ke



      reply	other threads:[~2026-03-24  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  1:58 [PATCH rtw-next] wifi: rtw88: validate RX rate to prevent out-of-bound Ping-Ke Shih
2026-03-24  0:17 ` LB F
2026-03-24  1:07   ` Ping-Ke Shih [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=27c838b55d794708b875fef31758ae8e@realtek.com \
    --to=pkshih@realtek.com \
    --cc=goainwo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox