From: syzbot <syzbot+list03bbbf1a526b820eedf1@syzkaller.appspotmail.com>
To: jmaloy@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net
Subject: [syzbot] Monthly tipc report (Feb 2026)
Date: Thu, 19 Feb 2026 23:32:23 -0800 [thread overview]
Message-ID: <69980e07.050a0220.21cd75.01b8.GAE@google.com> (raw)
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 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:[~2026-02-20 7:32 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=69980e07.050a0220.21cd75.01b8.GAE@google.com \
--to=syzbot+list03bbbf1a526b820eedf1@syzkaller.appspotmail.com \
--cc=jmaloy@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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