From: syzbot <syzbot+5b3e7c7a0b77f0c03b0d@syzkaller.appspotmail.com>
To: cpaasch@apple.com, davem@davemloft.net, edumazet@google.com,
geliang.tang@linux.dev, geliang@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, martineau@kernel.org,
matttbe@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mptcp?] WARNING in __mptcp_clean_una
Date: Tue, 30 Jul 2024 19:00:03 -0700 [thread overview]
Message-ID: <000000000000dce735061e8173dc@google.com> (raw)
In-Reply-To: <0000000000005dc7ce0611833268@google.com>
syzbot suspects this issue was fixed by commit:
commit fb7a0d334894206ae35f023a82cad5a290fd7386
Author: Paolo Abeni <pabeni@redhat.com>
Date: Mon Apr 29 18:00:31 2024 +0000
mptcp: ensure snd_nxt is properly initialized on connect
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c8bdbd980000
start commit: 4f5e5092fdbf Merge tag 'net-6.8-rc5' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1d7c92dd8d5c7a1e
dashboard link: https://syzkaller.appspot.com/bug?extid=5b3e7c7a0b77f0c03b0d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fc9c8a180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d0cc1c180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mptcp: ensure snd_nxt is properly initialized on connect
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-07-31 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 17:37 [syzbot] [mptcp?] WARNING in __mptcp_clean_una syzbot
2024-07-31 2:00 ` syzbot [this message]
2024-07-31 9:59 ` Paolo Abeni
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=000000000000dce735061e8173dc@google.com \
--to=syzbot+5b3e7c7a0b77f0c03b0d@syzkaller.appspotmail.com \
--cc=cpaasch@apple.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang.tang@linux.dev \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).