Re: [dm-devel] [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace

2020-12-16 Thread Vitaly Mayatskih
On Mon, Dec 14, 2020 at 10:03 PM Palmer Dabbelt wrote: > I was really experting someone to say that. It does seem kind of silly to > build > out the new interface, but not go all the way to a ring buffer. We just > didn't > really have any way to justify the extra complexity as our use cases

Re: [PATCH v7 2/3] dmaengine: ptdma: register PTDMA controller as a DMA resource

2020-11-24 Thread Vitaly Mayatskih
On Tue, Nov 24, 2020 at 12:18 PM Vinod Koul wrote: > IIRC there were few issues that I would like to get fixed before we can > apply.. I hope authors can reply to the comments received and we can > discuss on this. Sounds like a plan, thanks! -- wbr, Vitaly

Re: [PATCH v7 2/3] dmaengine: ptdma: register PTDMA controller as a DMA resource

2020-11-24 Thread Vitaly Mayatskih
On Wed, Nov 18, 2020 at 7:20 AM Vinod Koul wrote: > this should be single line Vinod, do you see any obvious functional defects still present in the driver, or can it be finally merged for us to start testing, while Sanjay is working on improvements and style fixes? I'm sure the driver has

Re: [PATCH] md: fix deadlock causing by sysfs_notify

2020-07-16 Thread Vitaly Mayatskih
We saw it as well (and fixed a bit differently, because of kpatch). Here's the reproducer, triggers the bug within few seconds for i in {0..3}; do dd if=/dev/zero of=/dev/shm/$i bs=512M count=1 losetup /dev/loop$((4+i)) /dev/shm/$i done sleep 1 yes | mdadm -C /dev/md0 -l10 -n4

Re: [PATCH] vhost: zero vhost_vsock memory on allocation

2019-03-28 Thread Vitaly Mayatskih
On Thu, Mar 28, 2019 at 12:36 PM Stefan Hajnoczi wrote: > vsock->hash is only read if vsock->guest_cid has already been set and > hence vsock->hash has been initialized too. I don't see where the > problem is. > > Was your tree missing commit a72b69dc083a931422cc8a5e33841aff7d5312f2 >

Re: [PATCH] vhost: zero vhost_vsock memory on allocation

2019-03-27 Thread Vitaly Mayatskih
On Wed, Mar 27, 2019 at 12:49 PM Stefan Hajnoczi wrote: > Which field was accessed before initialization? > > I ask because the situation is now unclear since code remains that > assumes vsock is *not* zero-initialized: > > vsock->guest_cid = 0; /* no CID assigned yet */ > >

Re: [PATCH 0/1] vhost: add vhost_blk driver

2018-11-02 Thread Vitaly Mayatskih
Sure! It needs a new QEMU driver (vhost-blk-pci), I'm preparing it to be sent out. On Fri, Nov 2, 2018 at 2:26 PM Michael S. Tsirkin wrote: > > On Fri, Nov 02, 2018 at 06:21:22PM +, Vitaly Mayatskikh wrote: > > vhost_blk is a host-side kernel mode accelerator for virtio-blk. The > > driver

Re: [PATCH 0/1] vhost: add vhost_blk driver

2018-11-02 Thread Vitaly Mayatskih
Sure! It needs a new QEMU driver (vhost-blk-pci), I'm preparing it to be sent out. On Fri, Nov 2, 2018 at 2:26 PM Michael S. Tsirkin wrote: > > On Fri, Nov 02, 2018 at 06:21:22PM +, Vitaly Mayatskikh wrote: > > vhost_blk is a host-side kernel mode accelerator for virtio-blk. The > > driver