From: syzbot <syzbot+13e1ee9caeab5a9abc62@syzkaller.appspotmail.com>
To: aviadye@mellanox.com, borisp@mellanox.com, davejwatson@fb.com,
davem@davemloft.net, gregkh@linuxfoundation.org,
ilyal@mellanox.com, kstewart@linuxfoundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pombredanne@nexb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: WARNING in sk_stream_kill_queues (3)
Date: Mon, 25 Nov 2019 07:59:01 -0800 [thread overview]
Message-ID: <00000000000093bc3b05982dd771@google.com> (raw)
In-Reply-To: <000000000000013b0d056e997fec@google.com>
syzbot has bisected this bug to:
commit 3c4d7559159bfe1e3b94df3a657b2cda3a34e218
Author: Dave Watson <davejwatson@fb.com>
Date: Wed Jun 14 18:37:39 2017 +0000
tls: kernel TLS support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=127a8f22e00000
start commit: be779f03 Merge tag 'kbuild-v4.18-2' of git://git.kernel.or..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=117a8f22e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=167a8f22e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=855fb54e1e019da2
dashboard link: https://syzkaller.appspot.com/bug?extid=13e1ee9caeab5a9abc62
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165a0c1f800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114591af800000
Reported-by: syzbot+13e1ee9caeab5a9abc62@syzkaller.appspotmail.com
Fixes: 3c4d7559159b ("tls: kernel TLS support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-25 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 12:47 WARNING in sk_stream_kill_queues (3) syzbot
2019-11-25 15:59 ` syzbot [this message]
2019-11-25 17:39 ` Jakub Kicinski
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=00000000000093bc3b05982dd771@google.com \
--to=syzbot+13e1ee9caeab5a9abc62@syzkaller.appspotmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=ilyal@mellanox.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.