From: syzbot <syzbot+listd2daf64d46ed16abd4d5@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, martineau@kernel.org,
matttbe@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mptcp report (Oct 2025)
Date: Thu, 09 Oct 2025 09:31:30 -0700 [thread overview]
Message-ID: <68e7e362.050a0220.1186a4.0000.GAE@google.com> (raw)
Hello mptcp maintainers/developers,
This is a 31-day syzbot report for the mptcp subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/mptcp
During the period, 2 new issues were detected and 5 were fixed.
In total, 4 issues are still open and 33 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9 No WARNING in subflow_data_ready (4)
https://syzkaller.appspot.com/bug?extid=0ff6b771b4f7a5bce83b
<2> 1 No possible deadlock in mptcp_pm_nl_add_addr_doit
https://syzkaller.appspot.com/bug?extid=7fb125d1bae280dc4749
<3> 1 No possible deadlock in mptcp_subflow_create_socket (2)
https://syzkaller.appspot.com/bug?extid=fb2c3fa2ba28aec94627
---
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-10-09 16:31 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=68e7e362.050a0220.1186a4.0000.GAE@google.com \
--to=syzbot+listd2daf64d46ed16abd4d5@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--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