Re: [PATCH 17/18] unbindable mounts

[Andi Kleen]

Al Viro <viro@xxxxxxxxxxxxxxxx> writes:

> From: Ram Pai <linuxram@xxxxxxxxxx>
> Date: 1131402080 -0500
> 
> A unbindable mount does not forward or receive propagation. Also unbindable
> mount disallows bind mounts. The semantics is as follows.
> 
> Bind semantics:
>   Its invalid to bind mount a unbindable mount.
> Move semantics:
>   Its invalid to move a unbindable mount under shared mount.
> Clone-namespace semantics:
>   If a mount is unbindable in the parent namespace, the corresponding
>   cloned mount in the child namespace becomes unbindable too.  Note:
>   there is subtle difference, unbindable mounts cannot be bind mounted
>   but can be cloned during clone-namespace.

What is it good for?
Normally I would have expected that to be part of the description.


-Andi (slightly worried about all these different mount variants. Hopefully
you guys themselves can still keep them all in your heads)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/