...
> > BTW, while testing the updated patch, I noticed current master branch (as
> > of 10/08) fails to execute virtiofsd.
> > backtrace from coredump shows:
> > #0 get_relocated_path (dir=0x560f4d2f2ef0
> > "/usr/local/var/run/virtiofsd") at ../util/cutils.c:924
> > #1 0x0000560f4baab6da in qemu_get_local_state_pathname
> (relative_pathname=relative_pathname@entry=0x560f4bac6cf1 "run/virtiofsd")
> > at ../util/oslib-posix.c:345
> > #2 0x0000560f4baa1b09 in fv_socket_lock (se=0x560f4d2f2f20) at
> > ../tools/virtiofsd/fuse_virtio.c:865
> > #3 fv_create_listen_socket (se=0x560f4d2f2f20) at
> > ../tools/virtiofsd/fuse_virtio.c:906
> > #4 virtio_session_mount (se=0x560f4d2f2f20) at
> > ../tools/virtiofsd/fuse_virtio.c:968
> > #5 0x0000560f4ba99725 in main (argc=<optimized out>, argv=<optimized
> > out>) at ../tools/virtiofsd/passthrough_ll.c:2947
> >
> > So, this is related to:
> > https://github.com/qemu/qemu/commit/f4f5ed2cbde65acaa1bd88d00cc23fa8bf
> > 6b5ed9#diff-ae9b732998587b609c0854bae40b2fe6R924
> >
> > Adding "qemu_init_exec_dir(argv[0]);" in virtiofs's main() seems
> > solve the problem, but is it correct fix?
>
> Yes, I've already posted the fix for that,
> https://lists.gnu.org/archive/html/qemu-devel/2020-10/msg01852.html
>
Thanks, then test is ok and I will send v2.
Regards,
Misono
> Dave
>
> > Regards,
> > Misono
> >
> > >
> > > Thanks,
> > >
> > > Paolo
> > >
> > > > -have_virtiofsd = (have_system and
> > > > - have_tools and
> > > > - 'CONFIG_LINUX' in config_host and
> > > > - 'CONFIG_SECCOMP' in config_host and
> > > > - 'CONFIG_LIBCAP_NG' in config_host and
> > > > - 'CONFIG_VHOST_USER' in config_host)
> > > > -
> > > > -if have_virtiofsd
> > > > +if 'CONFIG_VIRTIOFSD' in config_host
> > > > subdir('virtiofsd')
> > > > endif
> > > >
> >
> >
> > _______________________________________________
> > Virtio-fs mailing list
> > virtio...@redhat.com
> > https://www.redhat.com/mailman/listinfo/virtio-fs
> --
> Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
