From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Zeshan Ahmed Nobin" <zeshanahmednobin@gmail.com>,
linux-wireless@vger.kernel.org
Cc: "Ping-Ke Shih" <pkshih@realtek.com>, "Kalle Valo" <kvalo@kernel.org>
Subject: Re: [PATCH rtw-next v2 0/2] wifi: rtw88: 8822c: check register values in cck_pd_set
Date: Sun, 08 Nov 2026 07:32:29 +0000 [thread overview]
Message-ID: <cec3629205b2535d73f5285caddec290e7bda1c4@linux.dev> (raw)
In-Reply-To: <20261107183403.50696-1-zeshanahmednobin@gmail.com>
Hi Zeshan,
November 7, 2026 at 7:34 PM, "Zeshan Ahmed Nobin" <zeshanahmednobin@gmail.com> wrote:
>
> rtw8822c_phy_cck_pd_set() indexes its tables with two values read from
> the chip, bw and nrx, without checking them first. When the chip stops
> responding, both can be out of range. Patch 1 handles bw, which goes out
> of range when an RTL8822CE drops off the PCIe bus. Patch 2 handles nrx,
> which Luka Gejak found while reviewing v1.
>
Do you mind resending this series and putting linux-kernel.vger.kernel.org
in the CC as well. linux- wireless@vger.kernel.org list seems to be
broken right now. Just change [PATCH] to [PATCH RESEND] and don't
change patches nor cover letter.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-11-08 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 18:34 [PATCH rtw-next v2 0/2] wifi: rtw88: 8822c: check register values in cck_pd_set Zeshan Ahmed Nobin
2026-11-07 18:34 ` [PATCH rtw-next v2 1/2] wifi: rtw88: 8822c: fix out-of-bounds access " Zeshan Ahmed Nobin
2026-11-07 18:34 ` [PATCH rtw-next v2 2/2] wifi: rtw88: 8822c: ignore nrx values without CCK PD registers Zeshan Ahmed Nobin
2026-11-08 7:32 ` Luka Gejak [this message]
2026-11-08 7:34 ` [PATCH rtw-next v2 0/2] wifi: rtw88: 8822c: check register values in cck_pd_set Luka Gejak
2026-11-09 2:10 ` Ping-Ke Shih
2026-11-09 6:06 ` Luka Gejak
2026-11-09 6:14 ` Ping-Ke Shih
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=cec3629205b2535d73f5285caddec290e7bda1c4@linux.dev \
--to=luka.gejak@linux.dev \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=zeshanahmednobin@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