Private loop devices with loopfs

Posted May 7, 2020 19:35 UTC (Thu) by NYKevin (subscriber, #129325)
Parent article: Private loop devices with loopfs

The Chromium OS docs have this line:

> If you have a use case that wouldn't be solved by supporting FUSE, please file a bug for us.

This does somewhat raise the question of whether FUSE is already an adequate replacement for loop devices in the context of containers. I imagine the answer is "No, because performance," but I would be very interested in seeing actual load tests and experimental results, if any exist.

Private loop devices with loopfs

Posted May 8, 2020 8:41 UTC (Fri) by scientes (guest, #83068) [Link] (2 responses)

Nobody has managed to make a performant secure multi-user filesystem yet. seL4 people made a first attempt which was not successful.

Private loop devices with loopfs

Posted May 8, 2020 12:17 UTC (Fri) by theonewolf (guest, #118690) [Link] (1 responses)

Could you elaborate by what you mean with "multi user" and "performant"?

Also, do you have a link describing the seL4 work?

Private loop devices with loopfs

Posted May 9, 2020 6:01 UTC (Sat) by edomaur (subscriber, #14520) [Link]

Multi user, probably as in "each layer of the fs can be freely read from any running container without security problems" ?

Private loop devices with loopfs

Posted May 11, 2020 6:53 UTC (Mon) by maxfragg (subscriber, #122266) [Link]

My answer would rather be a "no because of security/availability", by design FUSE allows to block the Kernel, which is a good reason not to use it in any true multi-user env.