From: syzbot <syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, martineau@kernel.org,
matthieu.baerts@tessares.net, 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_check_listen_stop
Date: Thu, 14 Dec 2023 19:20:04 -0800 [thread overview]
Message-ID: <000000000000544e17060c83e034@google.com> (raw)
In-Reply-To: <0000000000004f4579060c68431b@google.com>
syzbot has bisected this issue to:
commit 57fc0f1ceaa4016354cf6f88533e20b56190e41a
Author: Paolo Abeni <pabeni@redhat.com>
Date: Tue Jun 20 16:24:23 2023 +0000
mptcp: ensure listener is unhashed before updating the sk status
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1279cb71e80000
start commit: 2513974cc3e1 Merge branch 'stmmac-bug-fixes'
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=1179cb71e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1679cb71e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b50bd31249191be8
dashboard link: https://syzkaller.appspot.com/bug?extid=5a01c3a666e726bc8752
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1119061ee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110ca006e80000
Reported-by: syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.com
Fixes: 57fc0f1ceaa4 ("mptcp: ensure listener is unhashed before updating the sk status")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-12-15 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 18:23 [syzbot] [mptcp?] WARNING in mptcp_check_listen_stop syzbot
2023-12-13 18:53 ` syzbot
2023-12-14 15:18 ` Paolo Abeni
2023-12-15 3:20 ` syzbot [this message]
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=000000000000544e17060c83e034@google.com \
--to=syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matthieu.baerts@tessares.net \
--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).