[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190919053620.GG2879@gauss3.secunet.de>
Date: Thu, 19 Sep 2019 07:36:20 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: syzbot <syzbot+f39ab8494f6015e62360@...kaller.appspotmail.com>,
<ast@...nel.org>, <aviadye@...lanox.com>, <borisp@...lanox.com>,
<bpf@...r.kernel.org>, <daniel@...earbox.net>,
<davejwatson@...com>, <davem@...emloft.net>, <ilyal@...lanox.com>,
<jakub.kicinski@...ronome.com>, <john.fastabend@...il.com>,
<kafai@...com>, <linux-crypto@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<songliubraving@...com>, <syzkaller-bugs@...glegroups.com>,
<yhs@...com>
Subject: Re: INFO: task hung in cancel_delayed_work_sync
On Wed, Sep 18, 2019 at 10:15:45PM -0700, Eric Biggers wrote:
>
> Reproducer involves pcrypt, so probably the pcrypt deadlock again...
> https://lkml.kernel.org/linux-crypto/20190817054743.GE8209@sol.localdomain/
I'll submit the patch I proposed here in case noone has a better idea
how to fix this now:
https://lkml.kernel.org/linux-crypto/20190821063704.GM2879@gauss3.secunet.de/
The original patch is from you, I did some modifications to forbid
pcrypt if an underlying algorithm needs a fallback.
May I leave your 'Signed off' on this patch, or just
quote that the initial version is from you?
Powered by blists - more mailing lists