search for: fuse_use_version

...diff --git a/src/fuse.c b/src/fuse.c index 2bd6787..349a5b9 100644 --- a/src/fuse.c +++ b/src/fuse.c @@ -25,6 +25,7 @@ #include <sys/types.h> #include <sys/wait.h> +#if HAVE_FUSE /* See <attr/xattr.h> */ #ifndef ENOATTR #define ENOATTR ENODATA @@ -32,7 +33,6 @@ #define FUSE_USE_VERSION 26 -#if HAVE_FUSE #include <fuse.h> #include <fuse_lowlevel.h> #endif -- 1.7.11.2.249.g31c7954

...<stdint.h> +#include <string.h> +#include <getopt.h> +#include <limits.h> +#include <fcntl.h> +#include <unistd.h> +#include <errno.h> +#include <signal.h> +#include <time.h> +#include <sys/types.h> +#include <sys/stat.h> + +#define FUSE_USE_VERSION 26 + +#include <fuse.h> +#include <fuse_lowlevel.h> + +#include <libnbd.h> + +#define MAX_REQUEST_SIZE (64 * 1024 * 1024) + +static struct nbd_handle *nbd; +static bool readonly = false; +static char *mountpoint, *filename; +static const char *pidfile; +static char *fuse_options;...

...@@ L<https://github.com/NetworkBlockDevice/nbd/blob/master/doc/uri.md>. > > L<libnbd-security(3)>, > L<nbdsh(1)>, > +L<nbdfuse(1)>, Worth sorting these two alphabetically? > L<qemu(1)>. > > +++ b/fuse/nbdfuse.c > + > +#define FUSE_USE_VERSION 26 > + > +#include <fuse.h> > +#include <fuse_lowlevel.h> > + > +#include <libnbd.h> > + > +#define MAX_REQUEST_SIZE (64 * 1024 * 1024) Although this works with nbdkit, qemu-nbd doesn't like more than 32M. (We really should find time to teach nbdkit/libn...

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever