Miklos Szeredi wrote:
> > Well, if you can find a way to tell the userspace FUSE daemon to know
> > that the mount is being done by the same user as the existing mount,
> > you don't need (or want) to check the credentials - you want the FUSE
> > daemon to tell the kernel code which superblock to reuse.
>
> It sounds very _very_ complicated compared to just using bind mounts.
>
> And maybe the user _does_ want a new connection to the same server
> (for whatever reason). Why should we _force_ a sharing of
> superblocks?
The point is that you can decide whether to do that in userspace.
It's up to whatever code you put in the _userspace_ FUSE commands.
No kernel support for bind mounts from another namespace is required.
Actually, in terms of complexity, it's not much different from using
bind mounts. Either way involves finding all the mounts of another
session and copying them one by one: either by getting confirmation
from the daemon to attach to the same superblock, or by getting
handles from the daemon for all the individual directories to bind
mount.
In all, I think private namespaces are still the cleaner way to do it
_when_ a user wants their mounts to appear in multiple sessions anyway.
But bind mounts or superblock sharing are more flexible, at the same
time as being more cumbersome as a user interface.
-- JAmie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
