From: Rolf Reintjes <rolf.reintjes@web.de>
To: Dan Carpenter <dan.carpenter@linaro.org>, qgeniecore@qualcomm.com
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] wifi: cfg80211: sme: store capped length in __cfg80211_connect_result()
Date: Wed, 3 Dec 2025 18:57:42 +0100 [thread overview]
Message-ID: <3204ebc0-4432-467c-81fe-9f09427b1671@web.de> (raw)
In-Reply-To: <aTAbp5RleyH_lnZE@stanley.mountain>
Hello Dan,
Am 03.12.2025 um 12:14 schrieb Dan Carpenter:
> The QGenie AI code review tool
Could you tell us more about this tool? Is there a web page of this
tool, how do you use this tool?
I found https://qgenie.ai/ but this is not a code review tool.
Rolf
> says we should store the capped length to
> wdev->u.client.ssid_len. The AI is correct.
>
> Fixes: 62b635dcd69c ("wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result()")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> net/wireless/sme.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/wireless/sme.c b/net/wireless/sme.c
> index 3a028ff287fb..4e629ca305bc 100644
> --- a/net/wireless/sme.c
> +++ b/net/wireless/sme.c
> @@ -910,7 +910,7 @@ void __cfg80211_connect_result(struct net_device *dev,
>
> ssid_len = min(ssid->datalen, IEEE80211_MAX_SSID_LEN);
> memcpy(wdev->u.client.ssid, ssid->data, ssid_len);
> - wdev->u.client.ssid_len = ssid->datalen;
> + wdev->u.client.ssid_len = ssid_len;
> break;
> }
> rcu_read_unlock();
next prev parent reply other threads:[~2025-12-03 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 11:14 [PATCH] wifi: cfg80211: sme: store capped length in __cfg80211_connect_result() Dan Carpenter
2025-12-03 17:57 ` Rolf Reintjes [this message]
2025-12-04 8:00 ` Dan Carpenter
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=3204ebc0-4432-467c-81fe-9f09427b1671@web.de \
--to=rolf.reintjes@web.de \
--cc=dan.carpenter@linaro.org \
--cc=johannes@sipsolutions.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=qgeniecore@qualcomm.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