From: syzbot <syzbot+0ff6b771b4f7a5bce83b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, mptcp@lists.linux.dev,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mptcp?] WARNING in subflow_data_ready (4)
Date: Wed, 26 Nov 2025 10:50:02 -0800 [thread overview]
Message-ID: <69274bda.a70a0220.d98e3.00e0.GAE@google.com> (raw)
In-Reply-To: <f697f3a0-859e-48bb-b0cd-28f176a24e2f@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0ff6b771b4f7a5bce83b@syzkaller.appspotmail.com
Tested-by: syzbot+0ff6b771b4f7a5bce83b@syzkaller.appspotmail.com
Tested on:
commit: ab084f0b drivers: net: fbnic: Return the true error in..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=153a1e92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1cc75ad16015d162
dashboard link: https://syzkaller.appspot.com/bug?extid=0ff6b771b4f7a5bce83b
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=121ba57c580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-26 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f697f3a0-859e-48bb-b0cd-28f176a24e2f@redhat.com>
2025-11-26 18:50 ` syzbot [this message]
[not found] <e5ede3d8-fba7-4e30-afae-85f6fffbfec7@redhat.com>
2025-11-27 8:03 ` [syzbot] [mptcp?] WARNING in subflow_data_ready (4) syzbot
2025-08-20 12:41 syzbot
2025-11-20 20:58 ` syzbot
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=69274bda.a70a0220.d98e3.00e0.GAE@google.com \
--to=syzbot+0ff6b771b4f7a5bce83b@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
--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