[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <829bc434-89e6-b17e-b832-d0d83480c80f@bytedance.com>
Date: Thu, 28 Sep 2023 09:24:29 +0800
From: zhenwei pi <pizhenwei@...edance.com>
To: "Michael S. Tsirkin" <mst@...hat.com>,
"Gonglei (Arei)" <arei.gonglei@...wei.com>
Cc: Halil Pasic <pasic@...ux.ibm.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
Marc Hartmayer <mhartmay@...ux.ibm.com>,
Jason Wang <jasowang@...hat.com>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Cornelia Huck <cohuck@...hat.com>
Subject: Re: Re: [PATCH] crypto: virtio-crypto: call finalize with bh disabled
Hi Michael & Lei,
I volunteer to fix this by workqueue.
I also notice that device drivers use workqueue to handle config-changed
again and again, what about re-implement __virtio_config_changed() by
kicking workqueue instead?
By the way, balloon dirvers uses
spin_lock_irqsave/spin_unlock_irqrestore in config-changed callback, do
it handle correctly?
On 9/27/23 21:25, Halil Pasic wrote:
> On Wed, 27 Sep 2023 09:24:09 +0000
> "Gonglei (Arei)" <arei.gonglei@...wei.com> wrote:
>
>>> On a related note, config change callback is also handled incorrectly in this
>>> driver, it takes a mutex from interrupt context.
>>
>> Good catch. Will fix it.
>
> Thanks Gonglei! Sorry I first misunderstood this as a problem within the
> virtio-ccw driver, but it is actually about virtio-crypto. Thanks for
> fixing this!
>
> Regards,
> Halil
--
zhenwei pi
Powered by blists - more mailing lists