From: syzbot <syzbot+189dcafc06865d38178d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [wireless?] WARNING in cfg80211_scan_done
Date: Thu, 19 Jun 2025 00:37:56 -0700 [thread overview]
Message-ID: <6853be54.050a0220.216029.01c0.GAE@google.com> (raw)
In-Reply-To: <000000000000dbcd0f061f911231@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [wireless?] WARNING in cfg80211_scan_done
Author: lizhi.xu@windriver.com
#syz test
diff --git a/net/wireless/scan.c b/net/wireless/scan.c
index e8a4fe44ec2d..bfd40797e608 100644
--- a/net/wireless/scan.c
+++ b/net/wireless/scan.c
@@ -1176,10 +1176,14 @@ void cfg80211_scan_done(struct cfg80211_scan_request *request,
struct cfg80211_scan_info *info)
{
struct cfg80211_scan_info old_info = request->info;
+ struct cfg80211_scan_request *rdev_req, *rdev_int_req;
+
+ rdev_req = wiphy_to_rdev(request->wiphy)->scan_req;
+ rdev_int_req = wiphy_to_rdev(request->wiphy)->int_scan_req;
trace_cfg80211_scan_done(request, info);
- WARN_ON(request != wiphy_to_rdev(request->wiphy)->scan_req &&
- request != wiphy_to_rdev(request->wiphy)->int_scan_req);
+ WARN_ON((rdev_req && request != rdev_req) &&
+ (rdev_int_req && request != rdev_int_req));
request->info = *info;
next prev parent reply other threads:[~2025-06-19 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 14:03 syzbot
2025-06-13 3:55 ` syzbot
2025-06-19 8:05 ` [PATCH] wifi: cfg80211: Prevent comparison with invalid registered dev scan req Lizhi Xu
2025-06-20 11:01 ` Johannes Berg
2025-06-23 8:26 ` Lizhi Xu
2025-06-19 2:52 ` [syzbot] Re: [syzbot] [wireless?] WARNING in cfg80211_scan_done syzbot
2025-06-19 7:37 ` syzbot [this message]
2026-01-05 17:04 ` syzbot
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=6853be54.050a0220.216029.01c0.GAE@google.com \
--to=syzbot+189dcafc06865d38178d@syzkaller.appspotmail.com \
--cc=linux-kernel@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®