From: syzbot <syzbot+4c9934f20522c0efd657@syzkaller.appspotmail.com>
To: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, lucien.xin@gmail.com,
marcelo.leitner@gmail.com, netdev@vger.kernel.org,
nhorman@tuxdriver.com, syzkaller-bugs@googlegroups.com,
vyasevich@gmail.com
Subject: Re: general protection fault in sctp_sched_rr_dequeue
Date: Mon, 11 Mar 2019 06:19:00 -0700 [thread overview]
Message-ID: <0000000000006f91c90583d16a9d@google.com> (raw)
In-Reply-To: <000000000000cc734405836318dc@google.com>
syzbot has bisected this bug to:
commit 7efba10d6bd22030fb5931e50bf97496f932f00e
Author: Xin Long <lucien.xin@gmail.com>
Date: Mon Jan 28 07:08:46 2019 +0000
sctp: add SCTP_FUTURE_ASOC and SCTP_CURRENT_ASSOC for
SCTP_STREAM_SCHEDULER sockopt
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14eec757200000
start commit: 7efba10d sctp: add SCTP_FUTURE_ASOC and SCTP_CURRENT_ASSOC..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=16eec757200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12eec757200000
kernel config: https://syzkaller.appspot.com/x/.config?x=872be05707464aaa
dashboard link: https://syzkaller.appspot.com/bug?extid=4c9934f20522c0efd657
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11cd9b03200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127de8e7200000
Reported-by: syzbot+4c9934f20522c0efd657@syzkaller.appspotmail.com
Fixes: 7efba10d ("sctp: add SCTP_FUTURE_ASOC and SCTP_CURRENT_ASSOC for
SCTP_STREAM_SCHEDULER sockopt")
prev parent reply other threads:[~2019-03-11 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 1:42 general protection fault in sctp_sched_rr_dequeue syzbot
2019-03-06 10:43 ` Xin Long
2019-03-06 12:03 ` Neil Horman
2019-03-07 17:50 ` Marcelo Ricardo Leitner
2019-03-11 13:19 ` 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=0000000000006f91c90583d16a9d@google.com \
--to=syzbot+4c9934f20522c0efd657@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.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).