From: syzbot <syzbot+list7655e841c85eeae9d270@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 (Dec 2024)
Date: Mon, 16 Dec 2024 01:44:21 -0800 [thread overview]
Message-ID: <675ff675.050a0220.37aaf.0124.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, 5 new issues were detected and 1 were fixed.
In total, 52 issues are still open and 146 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 56849 Yes WARNING in __ieee80211_beacon_get
https://syzkaller.appspot.com/bug?extid=18c783c5cf6a781e3e2c
<2> 6078 Yes WARNING in __cfg80211_ibss_joined (2)
https://syzkaller.appspot.com/bug?extid=7f064ba1704c2466e36d
<3> 4865 Yes WARNING in ath6kl_bmi_get_target_info (2)
https://syzkaller.appspot.com/bug?extid=92c6dd14aaa230be6855
<4> 3910 Yes WARNING in rate_control_rate_init (3)
https://syzkaller.appspot.com/bug?extid=9bdc0c5998ab45b05030
<5> 2200 Yes WARNING in __rate_control_send_low (3)
https://syzkaller.appspot.com/bug?extid=34463a129786910405dd
<6> 1844 Yes WARNING in plfxlc_mac_release
https://syzkaller.appspot.com/bug?extid=51a42f7c2e399392ea82
<7> 1183 Yes WARNING in ieee80211_start_next_roc
https://syzkaller.appspot.com/bug?extid=c3a167b5615df4ccd7fb
<8> 629 Yes INFO: task hung in rfkill_global_led_trigger_worker (3)
https://syzkaller.appspot.com/bug?extid=50499e163bfa302dfe7b
<9> 387 Yes INFO: task hung in crda_timeout_work (8)
https://syzkaller.appspot.com/bug?extid=d41f74db64598e0b5016
<10> 315 Yes INFO: task hung in reg_check_chans_work (7)
https://syzkaller.appspot.com/bug?extid=a2de4763f84f61499210
---
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:[~2024-12-16 9:44 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=675ff675.050a0220.37aaf.0124.GAE@google.com \
--to=syzbot+list7655e841c85eeae9d270@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