This is due to cgofuse registering its own handler that conflicts with ours.
This used to be stubbed out by this commit in our fork but the "go.mod" replace directive was dropped at some point during development.
We need to hard fork and/or coordinate with upstream about this. Since we have a similar problem on Windows with WinFSP.
We'd like cgofuse and WinFSP to have some mechanism to disable registering an interrupt handler, so that ours is always invoked.
For the former we can stub it out, for the latter I think this might be handled in the driver. If it is we can't change it easily due to driver signing requirements.
This is due to
cgofuse
registering its own handler that conflicts with ours. This used to be stubbed out by this commit in our fork but the "go.mod"replace
directive was dropped at some point during development.We need to hard fork and/or coordinate with upstream about this. Since we have a similar problem on Windows with WinFSP. We'd like
cgofuse
andWinFSP
to have some mechanism to disable registering an interrupt handler, so that ours is always invoked.For the former we can stub it out, for the latter I think this might be handled in the driver. If it is we can't change it easily due to driver signing requirements.