> > > Could also please explain why you want to go via user > > > mounts. Other OS use a daemon for that, which e.g. can maintain > > > access controls. How do you want to manage this? > > > > The unprivileged mounts patches do contain a simple form of access > > control. I don't think anything more is needed, but of course, having > > unprivileged mounts in the kernel does not prevent the use of a more > > sophisticated access control daemon in userspace, if that becomes > > necessary. > > A "I don't think anything more is needed" lets go off all sorts of warning > lights. Most things start out simple, so IMO it's very worth it to check > where it might go to to know the limits beforehand. The main question here > is why should a kernel based solution be preferable over a daemon based > solution? A daemon based solution would work for the "normal" case, where we have a single mount namespace and a single /etc/mtab file, and we hope it doesn't get too much out of sync with what is actually in the kernel (on remount the mount options do get out of sync, but hey, we seem to be able to live with that). However, once you start using multiple namespaces, the daemon based solution quickly becomes unusable, because you would need a separate daemon for each namespace, and it would have to somehow keep track of mount propagations in userspace (which is basically impossible), etc, etc... Does that answer your question? Thanks, Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
