From: syzbot <syzbot+list74a39cccbcbfcf70c2a9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Apr 2025)
Date: Wed, 09 Apr 2025 00:11:29 -0700 [thread overview]
Message-ID: <67f61da1.050a0220.258fea.0018.GAE@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 3 were fixed.
In total, 133 issues are still open and 1592 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 315729 Yes possible deadlock in team_del_slave (3)
https://syzkaller.appspot.com/bug?extid=705c61d60b091ef42c04
<2> 26386 Yes possible deadlock in smc_switch_to_fallback (2)
https://syzkaller.appspot.com/bug?extid=bef85a6996d1737c1a2f
<3> 12279 Yes possible deadlock in do_ip_setsockopt (4)
https://syzkaller.appspot.com/bug?extid=e4c27043b9315839452d
<4> 7795 Yes WARNING: suspicious RCU usage in dev_deactivate_queue
https://syzkaller.appspot.com/bug?extid=ca9ad1d31885c81155b6
<5> 6881 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<6> 6366 Yes KASAN: slab-use-after-free Read in __ethtool_get_link_ksettings
https://syzkaller.appspot.com/bug?extid=5fe14f2ff4ccbace9a26
<7> 6309 Yes WARNING in inet_sock_destruct (4)
https://syzkaller.appspot.com/bug?extid=de6565462ab540f50e47
<8> 3673 Yes possible deadlock in do_ipv6_setsockopt (4)
https://syzkaller.appspot.com/bug?extid=3433b5cb8b2b70933f8d
<9> 3315 Yes possible deadlock in sockopt_lock_sock
https://syzkaller.appspot.com/bug?extid=819a360379cf16b5f0d3
<10> 3195 Yes INFO: task hung in linkwatch_event (4)
https://syzkaller.appspot.com/bug?extid=2ba2d70f288cf61174e4
---
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:[~2025-04-09 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=67f61da1.050a0220.258fea.0018.GAE@google.com \
--to=syzbot+list74a39cccbcbfcf70c2a9@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.