From: syzbot <syzbot+listd6cd52ac5782bd942fe3@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Apr 2024)
Date: Tue, 30 Apr 2024 00:11:22 -0700 [thread overview]
Message-ID: <000000000000c7c09706174b1395@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, 10 new issues were detected and 23 were fixed.
In total, 79 issues are still open and 1428 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4504 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<2> 1404 Yes unregister_netdevice: waiting for DEV to become free (8)
https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
<3> 1077 Yes INFO: task hung in rfkill_global_led_trigger_worker (2)
https://syzkaller.appspot.com/bug?extid=2e39bc6569d281acbcfb
<4> 993 Yes INFO: task hung in switchdev_deferred_process_work (2)
https://syzkaller.appspot.com/bug?extid=8ecc009e206a956ab317
<5> 914 Yes INFO: task hung in rtnetlink_rcv_msg
https://syzkaller.appspot.com/bug?extid=8218a8a0ff60c19b8eae
<6> 534 Yes general protection fault in skb_release_data (2)
https://syzkaller.appspot.com/bug?extid=ccfa5775bc1bda21ddd1
<7> 457 Yes WARNING in inet_sock_destruct (4)
https://syzkaller.appspot.com/bug?extid=de6565462ab540f50e47
<8> 443 Yes WARNING in kcm_write_msgs
https://syzkaller.appspot.com/bug?extid=52624bdfbf2746d37d70
<9> 377 Yes INFO: rcu detected stall in tc_modify_qdisc
https://syzkaller.appspot.com/bug?extid=9f78d5c664a8c33f4cce
<10> 356 Yes KMSAN: uninit-value in bpf_prog_run_generic_xdp
https://syzkaller.appspot.com/bug?extid=0e6ddb1ef80986bdfe64
---
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-04-30 7:11 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=000000000000c7c09706174b1395@google.com \
--to=syzbot+listd6cd52ac5782bd942fe3@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).