On 8/10/26 12:49, Jonas Andradas wrote:
Package: virtiofsd
Version: 1.14.0-2
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
virtiofsd crashes with SIGSYS (seccomp) on the first request after a
client connects, making any VM with a virtiofs share fail to start.
This has been 100% reproducible on my host, standalone, with no libvirt
involved.
virtiofsd accepts the vhost-user socket connection successfully, then
is killed by its own seccomp filter (SIGSYS) apparently while calling
getsockopt(2) (syscall 55) — likely a SO_PEERCRED check on the newly
accepted socket, immediately after "Client connected, servicing
requests".
Do you have kernel message(s) about the issue? It should report which
syscall it disliked.
The issue is most likely not due to virtiofsd itself but due to a
recompile with more recent rustc or other crates, which now use more
syscalls when virtiofsd originally planned for. I mean, it is very
likely that a rebuild of 1.14.0-1 in current environment will also
be buggy.
Thanks,
/mjt
