On Mon, Jan 17, 2005 at 03:11:18PM -0500, Mike Waychison wrote: > I don't think that solves the problem. B should receive copies (with > shared semantics if called for) of all mountpoints C1,..,Cn that are > children of A if A->A. This is regardless of whether or not propagation > occurs before or after the attach.
... when that makes sense. Do you see any real problems with the proposed behaviour (i.e. propagation happens before attachment)? BTW, you do realize that rbind also has "copy before attaching" semantics, right? > Allowing this is like allowing directory aliasing in the sense that an > aliased directory that is nested within itself opens us to > badness/headaches 8) > > I still think the only way to handle this is to disallow vfsmounts in a > p-node to have (grand)parent-child relationships. This may have to be > extended to the 'owned by' case as well. Not feasible (and think what _that_ will do to --move, especially since propagation can span namespace boundaries). - 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/
