From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: syzbot <syzbot+503339bf3c9053b8a7fc@syzkaller.appspotmail.com>
Cc: aviadye@mellanox.com, borisp@mellanox.com, daniel@iogearbox.net,
davejwatson@fb.com, davem@davemloft.net,
john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: INFO: task hung in tls_sw_free_resources_tx
Date: Mon, 19 Aug 2019 14:16:14 -0700 [thread overview]
Message-ID: <20190819141614.10d5c07c@cakuba.netronome.com> (raw)
In-Reply-To: <000000000000cab053057c2e5202@google.com>
On Tue, 04 Dec 2018 00:48:02 -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 6915bf3b002b net: phy: don't allow __set_phy_supported to ..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=177085a3400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
> dashboard link: https://syzkaller.appspot.com/bug?extid=503339bf3c9053b8a7fc
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e6996d400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117e2125400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+503339bf3c9053b8a7fc@syzkaller.appspotmail.com
#syz dup: INFO: task hung in aead_recvmsg
prev parent reply other threads:[~2019-08-19 21:16 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
2019-08-19 21:16 ` Jakub Kicinski [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=20190819141614.10d5c07c@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+503339bf3c9053b8a7fc@syzkaller.appspotmail.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).