rfjakob

@NerdyProjects I just merged a [fix](https://github.com/rfjakob/gocryptfs/commit/af4c1fb7a3f428ff704af22294ad955d05ed41dd) into the gofuse_v2api branch (the current development branch). if you can try it, you'd just need to run git pull git checkout gofuse_v2api ./build.bash...

Yes I also see those, I'm not completely sure what is going on, but it seems like the kernel cifs driver and the Go multithreading don't like each other. But,...

One more thing I noticed when testing: When the **mountpoint** is on cifs, gocryptfs sometimes gets unmounted suddenly. For gocryptfs it looks like a regular unmount request. I'm not sure...

Maybe, in the sense that the Go runtime sends `SIGURG` to itself for multithreading interrupts. The theory is that cifs does not like it when the process that is accessing...

Looks like https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=88bc7d5097a1 has added `copy_file_range` support to FUSE in the Linux kernel. This may actually be possible now.

> Does this new `copy_file_range` call get mapped somehow to `FICLONE`? I *thought* it does. But looking at the kernel code, `FICLONE` seems to only call `clone_file_range`. The `copy_file_range` system...

Somebody else noticing that `cp` does not use `copy_file_range` in April 2018: https://lkml.org/lkml/2018/4/27/995

No, FICLONE uses clone_file_range

I guess the first step is finding (or writing) a userspace tool that actually uses copy_file_range. The building blocks in the kernel are there, I can add support to go-fuse.

Hehe. True, looks pretty useless, however, what if the file is actually a pipe?