From: syzbot <syzbot+list7f43769dfd404e5bafc6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly wireless report (Oct 2026)
Date: Mon, 05 Oct 2026 13:33:37 -0700 [thread overview]
Message-ID: <6ac409a1.ae2c267a.265a6c.0009.GAE@google.com> (raw)
Hello wireless maintainers/developers,
This is a 31-day syzbot report for the wireless subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/wireless
During the period, 2 new issues were detected and 10 were fixed.
In total, 18 issues are still open and 215 have already been fixed.
There are also 6 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1670 Yes INFO: task hung in reg_process_self_managed_hints
https://syzkaller.appspot.com/bug?extid=1f16507d9ec05f64210a
<2> 1007 No INFO: task hung in netdev_run_todo (4)
https://syzkaller.appspot.com/bug?extid=894cca71fa925aabfdb2
<3> 998 Yes INFO: task hung in crda_timeout_work (8)
https://syzkaller.appspot.com/bug?extid=d41f74db64598e0b5016
<4> 360 Yes INFO: task hung in ath9k_hif_usb_firmware_cb (3)
https://syzkaller.appspot.com/bug?extid=e9b1ff41aa6a7ebf9640
<5> 55 Yes INFO: task hung in nl80211_pre_doit (3)
https://syzkaller.appspot.com/bug?extid=da14e8c0ada830335981
<6> 19 Yes INFO: task hung in cfg80211_event_work (4)
https://syzkaller.appspot.com/bug?extid=5506b2556159a1ab6923
<7> 8 No BUG: workqueue lockup in reg_todo
https://syzkaller.appspot.com/bug?extid=b733a65a200ab7aa2cbe
<8> 6 Yes WARNING in __carl9170_tx_process_status
https://syzkaller.appspot.com/bug?extid=381102a7292a374fe8a7
<9> 1879 Yes INFO: task hung in reg_check_chans_work (7)
https://syzkaller.appspot.com/bug?extid=a2de4763f84f61499210
<10> 140 Yes INFO: task hung in regdb_fw_cb (2)
https://syzkaller.appspot.com/bug?extid=aff8125319e0457b4a25
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-10-05 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6ac409a1.ae2c267a.265a6c.0009.GAE@google.com \
--to=syzbot+list7f43769dfd404e5bafc6@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®