From: syzbot <syzbot+listf68cb1d62fb9bfa11103@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Jan 2024)
Date: Fri, 26 Jan 2024 13:54:29 -0800 [thread overview]
Message-ID: <00000000000021dcec060fe0575b@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, 3 new issues were detected and 15 were fixed.
In total, 70 issues are still open and 1384 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4010 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<2> 954 Yes possible deadlock in __dev_queue_xmit (3)
https://syzkaller.appspot.com/bug?extid=3b165dac15094065651e
<3> 883 Yes INFO: task hung in switchdev_deferred_process_work (2)
https://syzkaller.appspot.com/bug?extid=8ecc009e206a956ab317
<4> 778 Yes INFO: task hung in rfkill_global_led_trigger_worker (2)
https://syzkaller.appspot.com/bug?extid=2e39bc6569d281acbcfb
<5> 657 Yes INFO: task hung in rtnetlink_rcv_msg
https://syzkaller.appspot.com/bug?extid=8218a8a0ff60c19b8eae
<6> 432 Yes WARNING in kcm_write_msgs
https://syzkaller.appspot.com/bug?extid=52624bdfbf2746d37d70
<7> 324 Yes unregister_netdevice: waiting for DEV to become free (8)
https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
<8> 274 Yes INFO: rcu detected stall in tc_modify_qdisc
https://syzkaller.appspot.com/bug?extid=9f78d5c664a8c33f4cce
<9> 264 Yes BUG: corrupted list in p9_fd_cancelled (2)
https://syzkaller.appspot.com/bug?extid=1d26c4ed77bc6c5ed5e6
<10> 226 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.
reply other threads:[~2024-01-26 21: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=00000000000021dcec060fe0575b@google.com \
--to=syzbot+listf68cb1d62fb9bfa11103@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 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.