From: syzbot <syzbot+listce1365cc6514a1f8f55f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (May 2024)
Date: Thu, 30 May 2024 23:48:31 -0700 [thread overview]
Message-ID: <0000000000002ee1580619ba5fb4@google.com> (raw)
Hello net maintainers/developers,
This is a 31-day syzbot report for the net subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/net
During the period, 18 new issues were detected and 7 were fixed.
In total, 94 issues are still open and 1447 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 27358 Yes possible deadlock in team_del_slave (3)
https://syzkaller.appspot.com/bug?extid=705c61d60b091ef42c04
<2> 4787 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<3> 3655 Yes unregister_netdevice: waiting for DEV to become free (8)
https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
<4> 2060 Yes WARNING in skb_ensure_writable
https://syzkaller.appspot.com/bug?extid=0c4150bff9fff3bf023c
<5> 1243 Yes INFO: task hung in rfkill_global_led_trigger_worker (2)
https://syzkaller.appspot.com/bug?extid=2e39bc6569d281acbcfb
<6> 1214 Yes INFO: task hung in rtnetlink_rcv_msg
https://syzkaller.appspot.com/bug?extid=8218a8a0ff60c19b8eae
<7> 1067 Yes INFO: task hung in switchdev_deferred_process_work (2)
https://syzkaller.appspot.com/bug?extid=8ecc009e206a956ab317
<8> 990 Yes possible deadlock in __dev_queue_xmit (3)
https://syzkaller.appspot.com/bug?extid=3b165dac15094065651e
<9> 807 Yes possible deadlock in sock_map_delete_elem
https://syzkaller.appspot.com/bug?extid=4ac2fe2b496abca8fa4b
<10> 791 No INFO: task hung in addrconf_dad_work (4)
https://syzkaller.appspot.com/bug?extid=46af9e85f01be0118283
---
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-31 6:48 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=0000000000002ee1580619ba5fb4@google.com \
--to=syzbot+listce1365cc6514a1f8f55f@syzkaller.appspotmail.com \
--cc=linux-kernel@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