> no. there is no asymmetry as such. the propogations are working the way > they are meant to. But the confusion arises because of the mount lookup > symantics. The reason Avantika(who is doing shared subtree testing), > had this exact confusion is because of the 'most-recent-mount visible' > rule. I dont think this rule is documented anywhere. And the natural > response to such a behavior is confusion.
I really fail to see what you are getting at. You agree that: 1) mount doesn't propagate from /mnt/1 to /mnt/2/1. 2) mount propagates from /mnt/2/1 to /mnt/1. Then you are surprised that you don't see the same thing if you mount on /mnt/1 as if on /mnt/2/1. I think your proposed solution would be _more_ confusing not less, since then I'd not see the expected propagation from /mnt/2/1 to /mnt/1. I'd call that a bug. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
