From: Johannes Berg <johannes@sipsolutions.net>
To: Tristan Madani <tristmd@gmail.com>, Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: Re: [PATCH v3] wifi: rtw89: add bounds check on firmware mac_id in link lookup
Date: Tue, 21 Apr 2026 13:05:29 +0200 [thread overview]
Message-ID: <5160c46cda019dee1a01406fbd13cc0b9b02b3e2.camel@sipsolutions.net> (raw)
In-Reply-To: <20260421110133.2957818-1-tristmd@gmail.com> (sfid-20260421_130137_392604_8BC916E6)
On Tue, 2026-04-21 at 11:01 +0000, Tristan Madani wrote:
>
> diff --git a/drivers/net/wireless/realtek/rtw89/core.h b/drivers/net/wireless/realtek/rtw89/core.h
> index XXXXXXX..XXXXXXX 100644
> --- a/drivers/net/wireless/realtek/rtw89/core.h
> +++ b/drivers/net/wireless/realtek/rtw89/core.h
> @@ -6435,6 +6435,9 @@ static inline struct rtw89_sta_link *
> rtw89_assoc_link_rcu_dereference(struct rtw89_dev *rtwdev, u8 macid)
> {
> + if (unlikely(macid >= RTW89_MAX_MAC_ID_NUM))
> + return NULL;
> +
> return rcu_dereference(rtwdev->assoc_link_on_macid[macid]);
> }
Also, I have no idea how you're generating these patches, but please
don't do whatever you're doing.
You have "X-Mailer: git-send-email 2.47.3" in there, but there's no way
git would have created such corrupt patches. Also the "index XXXXX"
thing seems to point to some (fairly pointless since it's just hashes)
post-processing.
Please stop sending patches until you've figured out how to generate
patches that can actually (and reproducibly) be *applied*.
johannes
next prev parent reply other threads:[~2026-04-21 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 11:01 [PATCH v3] wifi: rtw89: add bounds check on firmware mac_id in link lookup Tristan Madani
2026-04-21 11:05 ` Johannes Berg [this message]
2026-04-21 11:08 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2026-04-21 11:14 Tristan Madani
2026-04-29 5:43 ` Ping-Ke Shih
2026-04-21 10:44 Tristan Madani
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=5160c46cda019dee1a01406fbd13cc0b9b02b3e2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=tristan@talencesecurity.com \
--cc=tristmd@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