search for: fuse_loop_mt

On Mon, Jun 26, 2017 at 10:27:54AM +0300, Maxim Kozover wrote: > I'd like to ask you, please, about multithreading with libguestfs. > I'm using libguestfs 1.36.4 with Perl front-end. > > Should it be possible to have the same libguestfs appliance provide both > fuse interface and periodically perform some longer APIs like find0? > > I mean make one Perl thread do

...chard! Maybe the function guestfs_mount_local_run shouldn't ACQUIRE_LOCK_FOR_CURRENT_SCOPE as it doesn't talk with the daemon and sits in the loop? What do you think? If I remove it from guestfs_mount_local_run (in lib/action-1.c, don't know how to properly remove it from ml generator), fuse_loop_mt works, but I still don't understand how it worked with fuse_loop (single threaded) when guestfs_mount_local_run did ACQUIRE_LOCK_FOR_CURRENT_SCOPE. Unfortunately multiple ls -lR to the same directory tree lead to crash while it seems multiple ls -lR to different directory trees (if not repeated...

...a negative result, maybe you could help, please? . > I'm using libguestfs-1.36.4 as a base since I changed for myself a bit some > detection stuff that you recently moved from C to OCaml and I can't rewrite > it immediately. > > WIth vanilla 1.36.4 just changing fuse_loop to fuse_loop_mt gives almost > immediate crash when the filesystem is accessed. That's expected because plain 1.36 doesn't support multithreading, but ... > I've put the most recent gnulib, changed a bit bootstrap etc, put the > patches from https://www.redhat.com/archives/libguestfs/2017-Ju...

On Mon, Oct 16, 2017 at 10:16:27PM +0300, Maxim Kozover wrote: > I mean if after applying multithreading patches I can change fuse_loop to > fuse_loop_mt... OK, I've not actually tested how well that works myself, so make sure you test it properly before doing anything important with it. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.co...

...th the daemon and sits > in the loop? What do you think? The lock is needed for any access to the guestfs_h structure, so I'm pretty sure that is not safe. > If I remove it from guestfs_mount_local_run (in lib/action-1.c, don't know > how to properly remove it from ml generator), fuse_loop_mt works, but I > still don't understand how it worked with fuse_loop (single threaded) when > guestfs_mount_local_run did ACQUIRE_LOCK_FOR_CURRENT_SCOPE. > Unfortunately multiple ls -lR to the same directory tree lead to crash > while it seems multiple ls -lR to different directory tr...

...gt;> >> The lock is needed for any access to the guestfs_h structure, so I'm >> pretty sure that is not safe. >> >> > If I remove it from guestfs_mount_local_run (in lib/action-1.c, don't >> know >> > how to properly remove it from ml generator), fuse_loop_mt works, but I >> > still don't understand how it worked with fuse_loop (single threaded) >> when >> > guestfs_mount_local_run did ACQUIRE_LOCK_FOR_CURRENT_SCOPE. >> > Unfortunately multiple ls -lR to the same directory tree lead to crash >> > while it se...