From: syzbot <syzbot+409b0354a6ba83a86aaf@syzkaller.appspotmail.com>
To: davem@davemloft.net, fw@strlen.de, kuba@kernel.org,
linux-kernel@vger.kernel.org, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net, mptcp@lists.01.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in mptcp_sendmsg_frag
Date: Fri, 19 Feb 2021 12:25:08 -0800 [thread overview]
Message-ID: <00000000000096022805bbb63f35@google.com> (raw)
In-Reply-To: <000000000000e29ec405bb8b9251@google.com>
syzbot has bisected this issue to:
commit 40947e13997a1cba4e875893ca6e5d5e61a0689d
Author: Florian Westphal <fw@strlen.de>
Date: Fri Feb 12 23:59:56 2021 +0000
mptcp: schedule worker when subflow is closed
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1541a434d00000
start commit: 773dc50d Merge branch 'Xilinx-axienet-updates'
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1741a434d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1341a434d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard link: https://syzkaller.appspot.com/bug?extid=409b0354a6ba83a86aaf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16548404d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150c2914d00000
Reported-by: syzbot+409b0354a6ba83a86aaf@syzkaller.appspotmail.com
Fixes: 40947e13997a ("mptcp: schedule worker when subflow is closed")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-02-19 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 17:30 general protection fault in mptcp_sendmsg_frag syzbot
2021-02-19 20:25 ` 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=00000000000096022805bbb63f35@google.com \
--to=syzbot+409b0354a6ba83a86aaf@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.01.org \
--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;
as well as URLs for NNTP newsgroup(s).