Messages in this thread | | | Subject | Re: [PATCH 12/18] shared mount handling: bind and rbind | From | Miklos Szeredi <> | Date | Tue, 08 Nov 2005 16:55:04 +0100 |
| |
> No. As explained in the same earlier threads; without this change the > behavior of shared-subtrees leads to inconsistency and confusion in some > scenarios. > > Under the premise that no application should depend on this behavior > (most-recent-mount-visible v/s top-most-mount-visible),
The strongest argument against was that
mount foo .; umount .
would no longer be a no-op.
> Al Viro permitted this change. And this is certainly the right > behavior.
Which is a contradiction in term, since you are saying that applications _do_ depend on it.
Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |