Re: [RFC 1/5] vduse: add virtio_fs to allowed dev id

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Eugenio Pérez <eperezma@xxxxxxxxxx>
Subject: Re: [RFC 1/5] vduse: add virtio_fs to allowed dev id
From: Jason Wang <jasowang@xxxxxxxxxx>
Date: Thu, 23 Jan 2025 09:48:03 +0800
Cc: linux-kernel@xxxxxxxxxxxxxxx, mst@xxxxxxxxxx, Hanna Reitz <hreitz@xxxxxxxxxx>, Stefano Garzarella <sgarzare@xxxxxxxxxx>, Xuan Zhuo <xuanzhuo@xxxxxxxxxxxxxxxxx>, Vivek Goyal <vgoyal@xxxxxxxxxx>, Miklos Szeredi <miklos@xxxxxxxxxx>, German Maglione <gmaglione@xxxxxxxxxx>, Stefan Hajnoczi <stefanha@xxxxxxxxxx>, virtualization@xxxxxxxxxxxxxxx
In-reply-to: <20250122163154.1225353-2-eperezma@redhat.com>
References: <20250122163154.1225353-1-eperezma@redhat.com> <20250122163154.1225353-2-eperezma@redhat.com>

On Thu, Jan 23, 2025 at 12:32 AM Eugenio Pérez <eperezma@xxxxxxxxxx> wrote:
>
> A VDUSE device that implements virtiofs device works fine just by
> adding the device id to the whitelist.
>
> Signed-off-by: Eugenio Pérez <eperezma@xxxxxxxxxx>

Acked-by: Jason Wang <jasowang@xxxxxxxxxx>

Thanks

References:
- [RFC 0/5] virtiofs: map buffer out of virtqueue lock
  - From: Eugenio Pérez
- [RFC 1/5] vduse: add virtio_fs to allowed dev id
  - From: Eugenio Pérez

Prev by Date: Re: [PATCH] virtio_blk: always post notifications under the lock
Next by Date: Re: [PATCH] vduse: add virtio_fs to allowed dev id
Previous by thread: [RFC 1/5] vduse: add virtio_fs to allowed dev id
Next by thread: [RFC 2/5] virtio_ring: introduce virtqueue_map/unmap_sgs()
Index(es):
- Date
- Thread

[Index of Archives] [KVM Development] [Libvirt Development] [Libvirt Users] [CentOS Virtualization] [Netdev] [Ethernet Bridging] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba]

Powered by Linux