From: syzbot <syzbot+c5a3099b94cbdd9cd6da@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, jmorris@namei.org,
kaber@trash.net, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, ncardwell@google.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
ycheng@google.com, yoshfuji@linux-ipv6.org
Subject: Re: WARNING in tcp_enter_loss (2)
Date: Fri, 29 Nov 2019 22:52:01 -0800 [thread overview]
Message-ID: <0000000000008c415905988ac808@google.com> (raw)
In-Reply-To: <001a113f39820d16d50567379661@google.com>
syzbot has bisected this bug to:
commit a0370b3f3f2cfb8b424b04c0545414abaa53f5ee
Author: Yuchung Cheng <ycheng@google.com>
Date: Fri Jan 13 06:11:36 2017 +0000
tcp: enable RACK loss detection to trigger recovery
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=114cbdf2e00000
start commit: 0644f186 Merge tag 'for_linus' of git://git.kernel.org/pub..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=134cbdf2e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=154cbdf2e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=61c12b53c2a25ec4
dashboard link: https://syzkaller.appspot.com/bug?extid=c5a3099b94cbdd9cd6da
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112146e7800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1317f95b800000
Reported-by: syzbot+c5a3099b94cbdd9cd6da@syzkaller.appspotmail.com
Fixes: a0370b3f3f2c ("tcp: enable RACK loss detection to trigger recovery")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-30 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a113f39820d16d50567379661@google.com>
2018-04-27 12:16 ` WARNING in tcp_enter_loss (2) syzbot
2019-11-30 6:52 ` 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=0000000000008c415905988ac808@google.com \
--to=syzbot+c5a3099b94cbdd9cd6da@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ycheng@google.com \
--cc=yoshfuji@linux-ipv6.org \
/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.