[Virtio-fs] [PATCH v7 0/6] virtiofsd: support per inode DAX

JeffleXu jefflexu at linux.alibaba.com
Thu Dec 9 01:41:58 UTC 2021



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.
> 

This warning can also be triggered in my test environment.

It seems that the warning will be triggered even with pure virtio-fs-dev
branch without my patches and latest kernel without my kernel patches.
Thus I didn't pay attention on it.

KVM warning:
    check_slave_message_entries: Short VhostUserFSSlaveMsg size, 8

virtiofsd warning:
    lo_destroy: unmap during destroy failed


-- 
Thanks,
Jeffle




More information about the Virtio-fs mailing list