[syzbot] Monthly tipc report (Feb 2026)

0 views
Skip to first unread message

syzbot

unread,
2:32 AM (20 hours ago) 2:32 AM
to jma...@redhat.com, linux-...@vger.kernel.org, net...@vger.kernel.org, syzkall...@googlegroups.com, tipc-di...@lists.sourceforge.net
Hello tipc maintainers/developers,

This is a 31-day syzbot report for the tipc subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/tipc

During the period, 0 new issues were detected and 0 were fixed.
In total, 5 issues are still open and 87 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 793 Yes INFO: rcu detected stall in corrupted (4)
https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
<2> 116 Yes BUG: soft lockup in do_sock_setsockopt
https://syzkaller.appspot.com/bug?extid=10a41dc44eef71aa9450
<3> 103 No INFO: rcu detected stall in sys_sendmmsg (7)
https://syzkaller.appspot.com/bug?extid=53e660acb94e444b9d63
<4> 47 Yes INFO: rcu detected stall in sock_close (5)
https://syzkaller.appspot.com/bug?extid=9a29e1dba699b6f46a03
<5> 32 Yes KMSAN: uninit-value in tipc_rcv (2)
https://syzkaller.appspot.com/bug?extid=9a4fbb77c9d4aacd3388

---
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 syzk...@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 all
Reply to author
Forward
0 new messages