[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190819143551.5b8935f5@cakuba.netronome.com>
Date: Mon, 19 Aug 2019 14:35:51 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Steffen Klassert <steffen.klassert@...unet.com>,
syzbot <syzbot+6a9ff159672dfbb41c95@...kaller.appspotmail.com>,
ast@...nel.org, aviadye@...lanox.com, borisp@...lanox.com,
bpf@...r.kernel.org, daniel@...earbox.net, davejwatson@...com,
davem@...emloft.net, hdanton@...a.com, john.fastabend@...il.com,
netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com,
herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org
Subject: Re: INFO: task hung in tls_sw_release_resources_tx
On Mon, 19 Aug 2019 14:12:55 -0700, Jakub Kicinski wrote:
> Looks like the dup didn't tickle syzbot the right way. Let me retry
> sending this directly to the original report.
Oh, no, my bad, there was just a third bug of the same nature.
tls_sw_release_resources_tx got renamed at some point, hence
the duplicate report.
Powered by blists - more mailing lists