From: syzbot <syzbot+ca1345cca66556f3d79b@syzkaller.appspotmail.com>
To: a@unstable.cc, aviadye@mellanox.com, aviadye@nvidia.com,
b.a.t.m.a.n@lists.open-mesh.org, borisp@mellanox.com,
borisp@nvidia.com, daniel@iogearbox.net, davem@davemloft.net,
idosch@mellanox.com, john.fastabend@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
netdev@vger.kernel.org, petrm@mellanox.com,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in tls_sk_proto_close
Date: Sat, 29 Aug 2020 11:23:07 -0700 [thread overview]
Message-ID: <000000000000d8002705ae084273@google.com> (raw)
In-Reply-To: <000000000000d3d67f05a20d2027@google.com>
syzbot has bisected this issue to:
commit 02d21b59d5cc4b4b395bbc2a29319b8a529ebeff
Author: Ido Schimmel <idosch@mellanox.com>
Date: Wed Jan 23 14:32:59 2019 +0000
mlxsw: spectrum_nve: Enable VXLAN on Spectrum-2
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e89b05900000
start commit: 5438dd45 net_sched: fix error path in red_init()
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=16e89b05900000
console output: https://syzkaller.appspot.com/x/log.txt?x=12e89b05900000
kernel config: https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=ca1345cca66556f3d79b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14acdfe5900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1792598e900000
Reported-by: syzbot+ca1345cca66556f3d79b@syzkaller.appspotmail.com
Fixes: 02d21b59d5cc ("mlxsw: spectrum_nve: Enable VXLAN on Spectrum-2")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-29 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:09 INFO: task hung in tls_sk_proto_close syzbot
2020-08-29 6:09 ` syzbot
2020-08-29 18:23 ` 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=000000000000d8002705ae084273@google.com \
--to=syzbot+ca1345cca66556f3d79b@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=aviadye@mellanox.com \
--cc=aviadye@nvidia.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=borisp@mellanox.com \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--cc=sw@simonwunderlich.de \
--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).