On Fri, Dec 10, 2021 at 10:54:20AM +0800, JeffleXu wrote: > Hi Vivek, > > Besides, I'd like to know that, to make the per inode DAX feature merged > into v5.17, shall the patches for virtiofsd also be ready during the > merge window?
I think having virtiofsd patches ready is not a strict requirement to merge kernel patches. I will provide my ack for the kernel patches. After that it is up to the Miklos to accept or reject those patches. Thanks Vivek > > > On 12/9/21 4:05 AM, Vivek Goyal wrote: > > On Wed, Dec 08, 2021 at 09:38:45AM +0800, JeffleXu wrote: > >> > >> > >> On 12/7/21 10:42 PM, Vivek Goyal wrote: > >>> Hi Jeffle, > >>> > >>> I noticed that you posted V8 of kernel patches. I was away from work > >>> so could not look at it. Now I am back and want to review and test > >>> those patches. > >> > >> Thanks for reviewing and evaluating. > >> > >>> > >>> Is there a new version of patches for virtiofsd as well? > >> > >> Nope. Patches for virtiofsd is not updated. v7 is the latest version. > > > > Hi Jeffle, > > > > I am testing these patches now. Using virtio-fs-dev branch and your > > patches on top. > > > > When I unmount virtiofs in guest, I see following qemu-kvm message > > on console. > > > > qemu-kvm: check_slave_message_entries: Short VhostUserFSSlaveMsg size, 8 > > > > Wondering have you noticed it. I have not debugged it. Wondering if > > it is due to your patches or there is something in virtio-fs-dev > > branch patches which triggers it. > > > > Vivek > > > > -- > Thanks, > Jeffle > _______________________________________________ Virtio-fs mailing list [email protected] https://listman.redhat.com/mailman/listinfo/virtio-fs
