On Mon, Apr 24, 2023 at 8:32 AM Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > > > The security model needs to be thought about and documented. Think > about this: the fuse server now delegates operations it would itself > perform to the passthrough code in fuse. The permissions that would > have been checked in the context of the fuse server are now checked in > the context of the task performing the operation. The server may be > able to bypass seccomp restrictions. Files that are open on the > backing filesystem are now hidden (e.g. lsof won't find these), which > allows the server to obfuscate accesses to backing files. Etc. > > These are not particularly worrying if the server is privileged, but > fuse comes with the history of supporting unprivileged servers, so we > should look at supporting passthrough with unprivileged servers as > well. > This is on my todo list. My current plan is to grab the creds that the daemon uses to respond to FUSE_INIT. That should keep behavior fairly similar. I'm not sure if there are cases where the fuse server is operating under multiple contexts. I don't currently have a plan for exposing open files via lsof. Every such file should relate to one that will show up though. I haven't dug into how that's set up, but I'm open to suggestions. > My other generic comment is that you should add justification for > doing this in the first place. I guess it's mainly performance. So > how performance can be won in real life cases? It would also be good > to measure the contribution of individual ops to that win. Is there > another reason for this besides performance? > > Thanks, > Miklos Our main concern with it is performance. We have some preliminary numbers looking at the pure passthrough case. We've been testing using a ramdrive on a somewhat slow machine, as that should highlight differences more. We ran fio for sequential reads, and random read/write. For sequential reads, we were seeing libfuse's passthrough_hp take about a 50% hit, with fuse-bpf not being detectably slower. For random read/write, we were seeing a roughly 90% drop in performance from passthrough_hp, while fuse-bpf has about a 7% drop in read and write speed. When we use a bpf that traces every opcode, that performance hit increases to a roughly 1% drop in sequential read performance, and a 20% drop in both read and write performance for random read/write. We plan to make more complex bpf examples, with fuse daemon equivalents to compare against. We have not looked closely at the impact of individual opcodes yet. There's also a potential ease of use for fuse-bpf. If you're implementing a fuse daemon that is largely mirroring a backing filesystem, you only need to write code for the differences in behavior. For instance, say you want to remove image metadata like location. You could give bpf information on what range of data is metadata, and zero out that section without having to handle any other operations. -Daniel
