From: syzbot <syzbot+list0eee01f891cd031c3139@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 (May 2024)
Date: Mon, 06 May 2024 06:18:34 -0700 [thread overview]
Message-ID: <0000000000000ab1040617c8e8da@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 0 were fixed.
In total, 28 issues are still open and 124 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8381 Yes WARNING in ieee80211_link_info_change_notify (2)
https://syzkaller.appspot.com/bug?extid=de87c09cc7b964ea2e23
<2> 7730 Yes WARNING in __ieee80211_beacon_get
https://syzkaller.appspot.com/bug?extid=18c783c5cf6a781e3e2c
<3> 4438 Yes WARNING in __cfg80211_ibss_joined (2)
https://syzkaller.appspot.com/bug?extid=7f064ba1704c2466e36d
<4> 3478 Yes WARNING in ieee80211_rx_list
https://syzkaller.appspot.com/bug?extid=8830db5d3593b5546d2e
<5> 879 Yes WARNING in ar5523_submit_rx_cmd/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=6101b0c732dea13ea55b
<6> 774 Yes WARNING in ieee80211_start_next_roc
https://syzkaller.appspot.com/bug?extid=c3a167b5615df4ccd7fb
<7> 79 Yes WARNING in ieee80211_free_ack_frame (2)
https://syzkaller.appspot.com/bug?extid=ac648b0525be1feba506
<8> 10 Yes INFO: task hung in reg_check_chans_work (6)
https://syzkaller.appspot.com/bug?extid=b87c222546179f4513a7
<9> 7 Yes WARNING in drv_remove_interface
https://syzkaller.appspot.com/bug?extid=2e5c1e55b9e5c28a3da7
<10> 5 Yes UBSAN: array-index-out-of-bounds in htc_issue_send
https://syzkaller.appspot.com/bug?extid=93cbd5fbb85814306ba1
---
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-05-06 13:18 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=0000000000000ab1040617c8e8da@google.com \
--to=syzbot+list0eee01f891cd031c3139@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).