search for: fuse_operations

...everything (he will have access to the image anyway). Of course, it should also be possible to give -o default_permissions to have the kernel check the permissions, which could be useful for some use cases. Now the strange thing is that the guestmount command implements the access function in fuse_operations. This results in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1761563 I have been asked to ask here for clarification on certain points: 1) If the above behaviour is wanted (no access checks without "-o default_permissions"; the expected checks by the kernel if the o...

...path); + + /* Just a stub. This method is called whenever FUSE wants to flush the + * pending changes (f.ex. to attributes) to a file. Since we don't have + * anything to do and don't want FUSE to think something went badly, + * just return 0. + */ + return 0; +} + static struct fuse_operations mount_local_operations = { .getattr = mount_local_getattr, .access = mount_local_access, @@ -902,6 +916,7 @@ static struct fuse_operations mount_local_operations = { .getxattr = mount_local_getxattr, .listxattr = mount_local_listxattr, .removexattr = mount_local_removexattr, + .flus...

Upon seeing RWM Jones article "Using mount-local API from C" I became curious because I thought there WAS a way to combine aspects of FUSE with the tools provided by libguestfs. So if I wanted to create my own filesystem using callbacks placed in the 'fuse_operations' struct (parameter to 'fuse_main()'), I could do so using guestfs. But after reading the article and looking at the 'guestmount' api it appears that fuse support is limited. Only the '-o' FUSE options can be passed and "only some of them are a good idea". So ho...

...size_t count, off_t offset, + struct fuse_file_info *fi); +static int nbdfuse_fsync (const char *path, int datasync, + struct fuse_file_info *fi); +static int nbdfuse_release (const char *path, struct fuse_file_info *fi); + +static struct fuse_operations fuse_operations = { + .getattr = nbdfuse_getattr, + .readdir = nbdfuse_readdir, + .open = nbdfuse_open, + .read = nbdfuse_read, + .write = nbdfuse_write, + .fsync = nbdfuse_fsync, + .release = nbdfuse_release, +}...

...re about it, but it's worth deciding if we want to care. > +} > + > +static void > +display_version (void) > +{ > + printf ("%s %s\n", PACKAGE_NAME, PACKAGE_VERSION); > +} > + > +static void > +fuse_help (const char *prog) > +{ > + static struct fuse_operations null_operations; > + const char *tmp_argv[] = { prog, "--help", NULL }; > + fuse_main (2, (char **) tmp_argv, &null_operations, NULL); > + exit (EXIT_SUCCESS); > +} > + > +static bool > +is_directory (const char *path) > +{ > + struct stat statbuf; >...

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

Hi, this series update libguestfs to a recent gnulib version, so that we can use its new getprogname module, and solve altogether one of the porting issues (the need for 'program_name' by the error module of gnulib), and have a single way to get the name of the current program. A number of changes in tools mostly, although mechanical. Thanks, Pino Toscano (3): Update gnulib to latest

...DECL_G (); @@ -824,7 +824,7 @@ mount_local_getxattr (const char *path, const char *name, char *value, } memcpy (value, xattrs->val[i].attrval, sz); -out: + out: if (free_attrs) guestfs_free_xattr_list ((struct guestfs_xattr_list *) xattrs); @@ -954,7 +954,7 @@ static struct fuse_operations mount_local_operations = { int guestfs_impl_mount_local (guestfs_h *g, const char *localmountpoint, - const struct guestfs_mount_local_argv *optargs) + const struct guestfs_mount_local_argv *optargs) { const char *t; struct fuse_args args = FUSE_ARGS_INIT (0, NUL...

Result of earlier copy and paste. --- align/scan.c | 35 ++++++++++--------- cat/cat.c | 39 +++++++++++---------- cat/filesystems.c | 69 +++++++++++++++++++------------------- cat/log.c | 35 ++++++++++--------- cat/ls.c | 61 +++++++++++++++++---------------- df/main.c | 43 ++++++++++++------------ diff/diff.c | 67

libguestfs has used double and triple underscores in identifiers. These aren't valid for global names in C++. (http://stackoverflow.com/a/228797) These large but completely mechanical patches change the illegal identifiers to legal ones. Rich.