From: syzbot <syzbot+list1dffa7f965b817f6f840@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 (Mar 2024)
Date: Tue, 05 Mar 2024 03:10:28 -0800 [thread overview]
Message-ID: <000000000000c690fb0612e7e30f@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 1 were fixed.
In total, 28 issues are still open and 121 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6920 Yes WARNING in __ieee80211_beacon_get
https://syzkaller.appspot.com/bug?extid=18c783c5cf6a781e3e2c
<2> 6045 Yes WARNING in ieee80211_link_info_change_notify (2)
https://syzkaller.appspot.com/bug?extid=de87c09cc7b964ea2e23
<3> 4412 Yes WARNING in __cfg80211_ibss_joined (2)
https://syzkaller.appspot.com/bug?extid=7f064ba1704c2466e36d
<4> 1222 Yes WARNING in __rate_control_send_low
https://syzkaller.appspot.com/bug?extid=fdc5123366fb9c3fdc6d
<5> 844 Yes WARNING in ar5523_submit_rx_cmd/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=6101b0c732dea13ea55b
<6> 750 Yes WARNING in ieee80211_start_next_roc
https://syzkaller.appspot.com/bug?extid=c3a167b5615df4ccd7fb
<7> 720 No INFO: task hung in ath9k_hif_usb_firmware_cb (2)
https://syzkaller.appspot.com/bug?extid=d5635158fb0281b27bff
<8> 73 Yes WARNING in ieee80211_free_ack_frame (2)
https://syzkaller.appspot.com/bug?extid=ac648b0525be1feba506
<9> 46 Yes WARNING in carl9170_usb_submit_cmd_urb/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=9468df99cb63a4a4c4e1
<10> 38 Yes WARNING in ar5523_cmd/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=1bc2c2afd44f820a669f
---
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-03-05 11:10 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=000000000000c690fb0612e7e30f@google.com \
--to=syzbot+list1dffa7f965b817f6f840@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.