From: Ping-Ke Shih <pkshih@realtek.com>
To: LB F <goainwo@gmail.com>,
Panagiotis Petrakopoulos <npetrakopoulos2003@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: Add NULL check for chip->edcca_th
Date: Tue, 14 Apr 2026 02:10:34 +0000 [thread overview]
Message-ID: <1e73055da16b40b59f20cdf63b82cb30@realtek.com> (raw)
In-Reply-To: <CALdGYqRLsPs8+kyAYphmKxfN9qF=1aGgn0O1LaASmjkDSUup_A@mail.gmail.com>
Hi Oleksandr,
LB F <goainwo@gmail.com> wrote:
> Ping-Ke, could you please take a look at this patch when you have a
> chance? If you approve the approach, I'll be happy to test it and
> provide a Tested-by.
I remember Bitterblue is still making a test patch, and this patch is one
to avoid garbage RX. If we can validate size or other clues at earlier of
RX data path, this malformed packet might not go into this function.
This reminds me, the patch getting merged to checking VHT rate seems to
be another clue of malformed packets. Maybe, we should just drop the
packets instead, which the content might be just a garbage.
Ping-Ke
next prev parent reply other threads:[~2026-04-14 2:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 10:02 [PATCH] wifi: rtw88: Add NULL check for chip->edcca_th Panagiotis Petrakopoulos
2026-04-13 12:35 ` LB F
2026-04-14 2:10 ` Ping-Ke Shih [this message]
2026-04-14 2:03 ` Ping-Ke Shih
2026-04-14 4:33 ` Panagiotis Petrakopoulos
2026-04-14 19:47 ` [PATCH v2] " Panagiotis Petrakopoulos
2026-04-15 0:36 ` Ping-Ke Shih
2026-04-15 5:29 ` [PATCH v3] wifi: rtw88: Add NULL check for chip->edcca_th in rtw_fw_adaptivity_result() Panagiotis Petrakopoulos
2026-04-15 5:54 ` Ping-Ke Shih
2026-04-15 17:03 ` LB F
2026-04-16 21:21 ` LB F
2026-04-17 5:48 ` Panagiotis Petrakopoulos
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=1e73055da16b40b59f20cdf63b82cb30@realtek.com \
--to=pkshih@realtek.com \
--cc=goainwo@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=npetrakopoulos2003@gmail.com \
/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