From: syzbot <syzbot+listaba4d9d9775b9482e752@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Nov 2023)
Date: Thu, 23 Nov 2023 05:12:23 -0800 [thread overview]
Message-ID: <00000000000029fce7060ad196ad@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, 5 new issues were detected and 13 were fixed.
In total, 77 issues are still open and 1358 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3878 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<2> 892 Yes possible deadlock in __dev_queue_xmit (3)
https://syzkaller.appspot.com/bug?extid=3b165dac15094065651e
<3> 860 Yes INFO: task hung in switchdev_deferred_process_work (2)
https://syzkaller.appspot.com/bug?extid=8ecc009e206a956ab317
<4> 590 Yes INFO: task hung in rtnetlink_rcv_msg
https://syzkaller.appspot.com/bug?extid=8218a8a0ff60c19b8eae
<5> 390 Yes WARNING in kcm_write_msgs
https://syzkaller.appspot.com/bug?extid=52624bdfbf2746d37d70
<6> 373 Yes INFO: rcu detected stall in corrupted (4)
https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
<7> 249 Yes INFO: rcu detected stall in tc_modify_qdisc
https://syzkaller.appspot.com/bug?extid=9f78d5c664a8c33f4cce
<8> 240 Yes BUG: corrupted list in p9_fd_cancelled (2)
https://syzkaller.appspot.com/bug?extid=1d26c4ed77bc6c5ed5e6
<9> 172 No INFO: task hung in linkwatch_event (3)
https://syzkaller.appspot.com/bug?extid=d4b2f8282f84f54e87a1
<10> 154 Yes WARNING in print_bfs_bug (2)
https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
---
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.
next reply other threads:[~2023-11-23 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 13:12 syzbot [this message]
2023-11-23 14:02 ` [syzbot] Monthly net report (Nov 2023) Jamal Hadi Salim
2023-11-28 15:05 ` Aleksandr Nogikh
2023-11-25 2:28 ` Jakub Kicinski
2023-11-28 14:54 ` Aleksandr Nogikh
2023-11-28 15:01 ` Jakub Kicinski
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=00000000000029fce7060ad196ad@google.com \
--to=syzbot+listaba4d9d9775b9482e752@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;
as well as URLs for NNTP newsgroup(s).