On Fri, Mar 02, 2018 at 08:58:26AM +0800, Fam Zheng wrote:
> On Thu, 03/01 14:54, Stefan Hajnoczi wrote:
> > On Thu, Mar 01, 2018 at 09:15:17AM +0800, Fam Zheng wrote:
> > > On Wed, 02/28 18:19, Stefan Hajnoczi wrote:
> > > > v2:
> > > > * Tackle the .ioeventfd_stop() vs vq handler race by removin
On Thu, 03/01 14:54, Stefan Hajnoczi wrote:
> On Thu, Mar 01, 2018 at 09:15:17AM +0800, Fam Zheng wrote:
> > On Wed, 02/28 18:19, Stefan Hajnoczi wrote:
> > > v2:
> > > * Tackle the .ioeventfd_stop() vs vq handler race by removing the
> > > ioeventfd
> > >from a BH in the IOThread [Fam]
> > >
On Thu, Mar 01, 2018 at 09:15:17AM +0800, Fam Zheng wrote:
> On Wed, 02/28 18:19, Stefan Hajnoczi wrote:
> > v2:
> > * Tackle the .ioeventfd_stop() vs vq handler race by removing the ioeventfd
> >from a BH in the IOThread [Fam]
> >
> > There are several race conditions in virtio-blk/virtio-sc
On Wed, 02/28 18:19, Stefan Hajnoczi wrote:
> v2:
> * Tackle the .ioeventfd_stop() vs vq handler race by removing the ioeventfd
>from a BH in the IOThread [Fam]
>
> There are several race conditions in virtio-blk/virtio-scsi dataplane code.
> This patch series addresses them, see the commit d
v2:
* Tackle the .ioeventfd_stop() vs vq handler race by removing the ioeventfd
from a BH in the IOThread [Fam]
There are several race conditions in virtio-blk/virtio-scsi dataplane code.
This patch series addresses them, see the commit description for details on the
individual cases.
Stefan
