From: Jakub Kicinski <kuba@kernel.org>
To: syzbot <syzbot+ba431dd9afc3a918981a@syzkaller.appspotmail.com>
Cc: andriin@fb.com, ast@kernel.org, aviadye@mellanox.com,
borisp@mellanox.com, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, john.fastabend@gmail.com, kafai@fb.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: INFO: task hung in tls_sw_cancel_work_tx
Date: Tue, 29 Dec 2020 11:08:38 -0800 [thread overview]
Message-ID: <20201229110838.7d3b080e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <000000000000861441059e047626@google.com>
On Fri, 07 Feb 2020 15:08:09 -0800 syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 90568ecf Merge tag 'kvm-5.6-2' of git://git.kernel.org/pub..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16513809e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=69fa012479f9a62
> dashboard link: https://syzkaller.appspot.com/bug?extid=ba431dd9afc3a918981a
> compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1036b6b5e00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1651f6e9e00000
#syz dup: INFO: task hung in tls_sk_proto_close
Looks like the exact same bug, perhaps syzbot got LTO enabled around
March which changed the function in which hung is reported..
prev parent reply other threads:[~2020-12-29 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 23:08 INFO: task hung in tls_sw_cancel_work_tx syzbot
2020-02-08 4:06 ` syzbot
2020-12-29 19:08 ` 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=20201229110838.7d3b080e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+ba431dd9afc3a918981a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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).