[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230927113612.3c46c20c.pasic@linux.ibm.com>
Date: Wed, 27 Sep 2023 11:36:12 +0200
From: Halil Pasic <pasic@...ux.ibm.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: "Gonglei (Arei)" <arei.gonglei@...wei.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>,
"pizhenwei@...edance.com" <pizhenwei@...edance.com>,
Cornelia Huck <cohuck@...hat.com>,
Halil Pasic <pasic@...ux.ibm.com>
Subject: Re: [PATCH] crypto: virtio-crypto: call finalize with bh disabled
On Tue, 26 Sep 2023 13:13:51 -0400
"Michael S. Tsirkin" <mst@...hat.com> wrote:
> > On the other hand virtio_airq_handler() calls vring_interrupt() with
> > interrupts enabled. (While vring_interrupt() is called in a (read)
> > critical section in virtio_airq_handler() we use read_lock() and
> > not read_lock_irqsave() to grab the lock. Whether that is correct in
> > it self (i.e. disregarding the crypto problem) or not I'm not sure right
> > now. Will think some more about it tomorrow.) If the way to go forward
> > is disabling interrupts in virtio-ccw before vring_interrupt() is
> > called, I would be glad to spin a patch for that.
> >
> > Copying Conny, as she may have an opinion on this (if I'm not wrong she
> > authored that code).
> >
> > Regards,
> > Halil
>
> On a related note, config change callback is also handled incorrectly
> in this driver, it takes a mutex from interrupt context.
Thanks Michael! I intend to give Connie a little more time to chime in.
Assumed no controversies emerge I intend to cook up two patches for
the two issues later during the day.
Regards,
Halil
Powered by blists - more mailing lists