From: syzbot <syzbot+listf0228ddbe98f29873fa7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Jun 2025)
Date: Fri, 13 Jun 2025 05:25:34 -0700 [thread overview]
Message-ID: <684c18be.a00a0220.279073.000f.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, 21 new issues were detected and 9 were fixed.
In total, 145 issues are still open and 1614 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 352391 Yes possible deadlock in team_del_slave (3)
https://syzkaller.appspot.com/bug?extid=705c61d60b091ef42c04
<2> 331292 Yes unregister_netdevice: waiting for DEV to become free (8)
https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
<3> 14606 Yes possible deadlock in team_device_event (3)
https://syzkaller.appspot.com/bug?extid=b668da2bc4cb9670bf58
<4> 8218 Yes KASAN: slab-use-after-free Read in __ethtool_get_link_ksettings
https://syzkaller.appspot.com/bug?extid=5fe14f2ff4ccbace9a26
<5> 7128 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<6> 6515 Yes WARNING in inet_sock_destruct (4)
https://syzkaller.appspot.com/bug?extid=de6565462ab540f50e47
<7> 3361 No BUG: sleeping function called from invalid context in dev_set_allmulti
https://syzkaller.appspot.com/bug?extid=368054937a6a7ead5f35
<8> 3242 Yes INFO: task hung in linkwatch_event (4)
https://syzkaller.appspot.com/bug?extid=2ba2d70f288cf61174e4
<9> 2581 Yes WARNING in rcu_check_gp_start_stall
https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa
<10> 1681 Yes INFO: task hung in del_device_store
https://syzkaller.appspot.com/bug?extid=6d10ecc8a97cc10639f9
---
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-06-13 12:25 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=684c18be.a00a0220.279073.000f.GAE@google.com \
--to=syzbot+listf0228ddbe98f29873fa7@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.