From: syzbot <syzbot+503339bf3c9053b8a7fc@syzkaller.appspotmail.com>
To: aviadye@mellanox.com, borisp@mellanox.com, daniel@iogearbox.net,
davejwatson@fb.com, davem@davemloft.net, ilyal@mellanox.com,
john.fastabend@gmail.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in tls_sw_free_resources_tx
Date: Fri, 22 Mar 2019 17:56:00 -0700 [thread overview]
Message-ID: <0000000000005e7c340584b86f64@google.com> (raw)
In-Reply-To: <000000000000cab053057c2e5202@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=10c2d407200000
start commit: 6915bf3b net: phy: don't allow __set_phy_supported to add ..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=12c2d407200000
console output: https://syzkaller.appspot.com/x/log.txt?x=14c2d407200000
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
dashboard link: https://syzkaller.appspot.com/bug?extid=503339bf3c9053b8a7fc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e6996d400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117e2125400000
Reported-by: syzbot+503339bf3c9053b8a7fc@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-03-23 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 8:48 INFO: task hung in tls_sw_free_resources_tx syzbot
2019-03-23 0:56 ` syzbot [this message]
2019-08-19 21:16 ` 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=0000000000005e7c340584b86f64@google.com \
--to=syzbot+503339bf3c9053b8a7fc@syzkaller.appspotmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ilyal@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--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).