From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Wentao Guan <guanwentao@uniontech.com>,
Sasha Levin <sashal@kernel.org>,
kartikey406 <kartikey406@gmail.com>
Cc: johannes <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 6.6.y] wifi: cfg80211: release locks on error in cfg80211_wext_siwgenie()
Date: Mon, 12 Oct 2026 19:09:04 +0530 [thread overview]
Message-ID: <2c0c5d51-197c-47fd-b002-ecff397a826e@oracle.com> (raw)
In-Reply-To: <tencent_54DE3A7910D4598F5676AE58@qq.com>
Hi Wentao,
On 10/10/26 10:04 am, Wentao Guan wrote:
> Sorry, it is for v6.6.158. cc the stable list.
>
this needs to be fixed on 5.15.y and 6.1.y.
This was reported here:
https://lore.kernel.org/all/93db0eae-f479-4343-a126-59987ae0dc22@oracle.com/
thanks for making a patch.
Are you planning to send it to other branches as well ?
thanks,
Harshit> BRs
> Wentao Guan
>
>> ---
>> net/wireless/wext-sme.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/wireless/wext-sme.c b/net/wireless/wext-sme.c
>> index cfa903eb0e82f..0e7c314bdeef0 100644
>> --- a/net/wireless/wext-sme.c
>> +++ b/net/wireless/wext-sme.c
>> @@ -354,8 +354,10 @@ int cfg80211_wext_siwgenie(struct net_device *dev,
>> /* nothing */
>> }
>>
>> - if (!for_each_element_completed(elem, extra, ie_len))
>> - return -EINVAL;
>> + if (!for_each_element_completed(elem, extra, ie_len)) {
>> + err = -EINVAL;
>> + goto out;
>> + }
>>
>> ie = kmemdup(extra, ie_len, GFP_KERNEL);
>> if (!ie) {
next prev parent reply other threads:[~2026-10-12 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 4:30 Wentao Guan
2026-10-10 4:34 ` Wentao Guan
2026-10-12 13:39 ` Harshit Mogalapalli [this message]
2026-10-12 14:32 ` [PATCH " Wentao Guan
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=2c0c5d51-197c-47fd-b002-ecff397a826e@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=guanwentao@uniontech.com \
--cc=johannes@sipsolutions.net \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®