On Tue, 13 May 2025 at 20:52, Joanne Koong <joannelkoong@xxxxxxxxx> wrote: > For getting from conn to fuse server pid, what about adding the server > pid to fuse's sysfs info? This use case has come up a few times in > production where we've encountered a stuck server and have wanted to > identify its pid. I have a patch on a branch I need to clean up and > send out for this, but it adds a new "info" file to > /sys/fs/fuse/connections/*/ where libfuse can write any identifying > info to that file like the server pid or name. If the connection gets > migrated to another process then libfuse is responsible for modifying > that to reflect the correct info. Fine, but then why not just write something in /var/run/fuse? Thanks, Miklos
