When creating a new mount in fuse3, there are places where errno is used where the function doesn't seem to set an actual errno. This can result in errors like: Success (os error 0) or other random errors.
This part1 of the Mount::new calls into fuse_session_new2 and fuse_session_mount3 which does not seem to directly set an errno.
PS. We tried to upgrade fuser a couple of days ago but some change seem to make things break for us. Haven't had time to figure this out but the errors spotted were very random because of this.
When creating a new mount in fuse3, there are places where
errnois used where the function doesn't seem to set an actualerrno. This can result in errors like:Success (os error 0)or other random errors.This part1 of the
Mount::newcalls intofuse_session_new2 andfuse_session_mount3 which does not seem to directly set an errno.PS. We tried to upgrade
fusera couple of days ago but some change seem to make things break for us. Haven't had time to figure this out but the errors spotted were very random because of this.Footnotes
https://github.com/cberner/fuser/blame/master/src/mnt/fuse3.rs#L38-L58 ↩
https://github.com/libfuse/libfuse/blob/59cf26a2d778b88819db528c67141b788a8b48a1/lib/fuse_lowlevel.c#L4321-L4380 ↩
https://github.com/libfuse/libfuse/blob/59cf26a2d778b88819db528c67141b788a8b48a1/lib/fuse_lowlevel.c#L4387-L4396 ↩