On Thu, Oct 10, 2013 at 1:43 PM, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > I have been weighing the pros and the cons of this. > > At this point the most practical path I can see is to block unlink, > rename, and rmdir if there is a mount in the local namespace. > > At the very least that makes very limited additions to what applications > can depend on from the vfs, and even more importantly that can be ready > by 3.13. > > Furthermore it removes the nasty need for filesystems to lie to the vfs, > and removes the nasty DOS that non-local mountpoints are. Agreed 100%. > Miklos if you as the fuse maintainer aren't worried about network > filesystems, and multiple namespaces I won't worry either. Especially > since modern versions of fuse aren't affected. I think the above conditions (local mount blocks unlink/rename) are enough to prevent most of the problems, of which there aren't many in any case. 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
