From: syzbot <syzbot+85e0b422ff140b03672a@syzkaller.appspotmail.com>
To: davem@davemloft.net, dvyukov@google.com,
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_assoc_rwnd_increase
Date: Sat, 16 Mar 2019 14:09:00 +0000 [thread overview]
Message-ID: <000000000000757009058436b23f@google.com> (raw)
In-Reply-To: <00000000000089bb100583e5fe7a@google.com>
In-Reply-To: <00000000000089bb100583e5fe7a@google.com>
syzbot has bisected this bug to:
commit 89664c623617b1d34447a927ac7871ddf3db29d3
Author: Xin Long <lucien.xin@gmail.com>
Date: Sun Mar 3 09:54:53 2019 +0000
sctp: sctp_sock_migrate() returns error if sctp_bind_addr_dup() fails
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x17b17777200000
start commit: 89664c62 sctp: sctp_sock_migrate() returns error if sctp_b..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x\x14717777200000
console output: https://syzkaller.appspot.com/x/log.txt?x\x10717777200000
kernel config: https://syzkaller.appspot.com/x/.config?x¶13f0327d980b6b
dashboard link: https://syzkaller.appspot.com/bug?extid…e0b422ff140b03672a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x12613b13200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x\x10f1884d200000
Reported-by: syzbot+85e0b422ff140b03672a@syzkaller.appspotmail.com
Fixes: 89664c62 ("sctp: sctp_sock_migrate() returns error if
sctp_bind_addr_dup() fails")
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+85e0b422ff140b03672a@syzkaller.appspotmail.com>
To: davem@davemloft.net, dvyukov@google.com,
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_assoc_rwnd_increase
Date: Sat, 16 Mar 2019 07:09:00 -0700 [thread overview]
Message-ID: <000000000000757009058436b23f@google.com> (raw)
In-Reply-To: <00000000000089bb100583e5fe7a@google.com>
syzbot has bisected this bug to:
commit 89664c623617b1d34447a927ac7871ddf3db29d3
Author: Xin Long <lucien.xin@gmail.com>
Date: Sun Mar 3 09:54:53 2019 +0000
sctp: sctp_sock_migrate() returns error if sctp_bind_addr_dup() fails
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b17777200000
start commit: 89664c62 sctp: sctp_sock_migrate() returns error if sctp_b..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14717777200000
console output: https://syzkaller.appspot.com/x/log.txt?x=10717777200000
kernel config: https://syzkaller.appspot.com/x/.config?x=b613f0327d980b6b
dashboard link: https://syzkaller.appspot.com/bug?extid=85e0b422ff140b03672a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12613b13200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f1884d200000
Reported-by: syzbot+85e0b422ff140b03672a@syzkaller.appspotmail.com
Fixes: 89664c62 ("sctp: sctp_sock_migrate() returns error if
sctp_bind_addr_dup() fails")
next prev parent reply other threads:[~2019-03-16 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 13:52 general protection fault in sctp_assoc_rwnd_increase syzbot
2019-03-12 13:52 ` syzbot
2019-03-12 16:29 ` Xin Long
2019-03-12 16:29 ` Xin Long
2019-03-12 17:26 ` Dmitry Vyukov
2019-03-12 17:26 ` Dmitry Vyukov
2019-03-18 6:25 ` Xin Long
2019-03-18 6:25 ` Xin Long
2019-03-16 14:09 ` syzbot [this message]
2019-03-16 14:09 ` syzbot
2019-03-17 13:17 ` Xin Long
2019-03-17 13:17 ` Xin Long
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=000000000000757009058436b23f@google.com \
--to=syzbot+85e0b422ff140b03672a@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.