From: syzbot <syzbot+aa0b64a57e300a1c6bcc@syzkaller.appspotmail.com>
To: 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,
vakul.garg@nxp.com
Subject: Re: INFO: task hung in __flush_work
Date: Thu, 21 Nov 2019 11:58:00 -0800 [thread overview]
Message-ID: <000000000000ecb2cb0597e0b62e@google.com> (raw)
In-Reply-To: <0000000000008f9c780581fd7417@google.com>
syzbot has bisected this bug to:
commit a42055e8d2c30d4decfc13ce943d09c7b9dad221
Author: Vakul Garg <vakul.garg@nxp.com>
Date: Fri Sep 21 04:16:13 2018 +0000
net/tls: Add support for async encryption of records for performance
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11bf7ecae00000
start commit: 90cadbbf Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=13bf7ecae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15bf7ecae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9d41c8529d7e7362
dashboard link: https://syzkaller.appspot.com/bug?extid=aa0b64a57e300a1c6bcc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a6629b400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1222d29b400000
Reported-by: syzbot+aa0b64a57e300a1c6bcc@syzkaller.appspotmail.com
Fixes: a42055e8d2c3 ("net/tls: Add support for async encryption of records
for performance")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-21 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 7:01 INFO: task hung in __flush_work syzbot
2019-11-21 19:58 ` 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=000000000000ecb2cb0597e0b62e@google.com \
--to=syzbot+aa0b64a57e300a1c6bcc@syzkaller.appspotmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vakul.garg@nxp.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).