From: syzbot <syzbot+list8aab4226317d7ca90415@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 (Aug 2024)
Date: Tue, 13 Aug 2024 01:54:21 -0700 [thread overview]
Message-ID: <0000000000007154d7061f8cc1c8@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, 34 issues are still open and 140 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 23665 Yes WARNING in __ieee80211_beacon_get
https://syzkaller.appspot.com/bug?extid=18c783c5cf6a781e3e2c
<2> 5497 Yes WARNING in __cfg80211_ibss_joined (2)
https://syzkaller.appspot.com/bug?extid=7f064ba1704c2466e36d
<3> 1109 Yes WARNING in ieee80211_start_next_roc
https://syzkaller.appspot.com/bug?extid=c3a167b5615df4ccd7fb
<4> 748 Yes WARNING in rate_control_rate_init (3)
https://syzkaller.appspot.com/bug?extid=9bdc0c5998ab45b05030
<5> 580 Yes WARNING in ath6kl_bmi_get_target_info (2)
https://syzkaller.appspot.com/bug?extid=92c6dd14aaa230be6855
<6> 214 Yes INFO: rcu detected stall in ieee80211_handle_queued_frames
https://syzkaller.appspot.com/bug?extid=1c991592da3ef18957c0
<7> 125 No INFO: task hung in rfkill_global_led_trigger_worker (3)
https://syzkaller.appspot.com/bug?extid=50499e163bfa302dfe7b
<8> 103 Yes WARNING in ieee80211_free_ack_frame (2)
https://syzkaller.appspot.com/bug?extid=ac648b0525be1feba506
<9> 60 No INFO: task hung in wiphy_unregister (2)
https://syzkaller.appspot.com/bug?extid=abba31ed4fc4178349e9
<10> 44 Yes WARNING in minstrel_ht_update_caps
https://syzkaller.appspot.com/bug?extid=d805aca692aded25f888
---
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-08-13 8:54 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=0000000000007154d7061f8cc1c8@google.com \
--to=syzbot+list8aab4226317d7ca90415@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.