Martin Pärtel
Martin Pärtel
Doesn't repro on a *very* slow AMD GX-412TC / Debian 11 either. > I've seen EACCES produced from openat,unlink, and stat thus far. This still feels like something outside bindfs...
Thank you for the very helpful script! Not sure what I did wrong previously, but the error now happens on my slow machine (Debian 11, kernel 5.10.0-21 fuse 2.9.9). But...
Ok, I've now seen it not repro in a Debian 11 VM (or Ubuntu 22.04 or 22.10) on the fast machine where it doesn't repro natively either. So the repro...
I think I now have pretty compelling evidence that this is a FUSE bug. I modified FUSE's [passthrough example's](https://github.com/libfuse/libfuse/blob/master/example/passthrough.c) to do user mirroring by adding the line stbuf->st_uid = fuse_get_context()->uid;...
FUSE devs don't want to treat this non-atomicity as a bug and told me to implement `access` instead. I'll try to find time to do that soon.
Thanks, I'm hopeful about finding the time in a few weeks. This probably just needs a few more hours of good concentration, but those have been in short supply :/
This would also allow `+` in addresses like [email protected], which would be good.
Workaround: ``` rocksdb = { git = "https://github.com/rust-rocksdb/rust-rocksdb", rev = "1cf906dc4087f06631820f13855e6b27bd21b972" } ``` The other commits between 0.22.0 and that one are very minor.
That and/or [Ww]atchrfile in the spirit of Makefiles :)
Hi! I'll take a closer look later, but this worries me: > Enabling this feature implicitly turns on the default_permissions mount option (even if it was not passed to mount(2))....