From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [RFC] shared subtrees Date: Sun, 16 Jan 2005 13:42:09 -0500 Message-ID: <20050116184209.GD13624@fieldses.org> References: <20050113221851.GI26051@parcelfarce.linux.theplanet.co.uk> <20050116160213.GB13624@fieldses.org> <20050116180656.GQ26051@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from dsl093-002-214.det1.dsl.speakeasy.net ([66.93.2.214]:37255 "EHLO pickle.fieldses.org") by vger.kernel.org with ESMTP id S262562AbVAPSmK (ORCPT ); Sun, 16 Jan 2005 13:42:10 -0500 To: Al Viro Content-Disposition: inline In-Reply-To: <20050116180656.GQ26051@parcelfarce.linux.theplanet.co.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sun, Jan 16, 2005 at 06:06:56PM +0000, Al Viro wrote: > On Sun, Jan 16, 2005 at 11:02:13AM -0500, J. Bruce Fields wrote: > > On Thu, Jan 13, 2005 at 10:18:51PM +0000, Al Viro wrote: > > > 6. mount --move > > > prohibited if what we are moving is in some p-node, otherwise we move > > > as usual to intended mountpoint and create copies for everything that > > > gets propagation from there (as we would do for rbind). > > > > Why this prohibition? > > How do you propagate that? We can weaken that to "in a p-node that > owns something or contains more than one vfsmount", but it's not > worth the trouble, AFAICS. I guess I'm not seeing what there is to propagate. If the vfsmount we are moving is mounted under a vfsmount that's in a p-node, then there'd be something to propagate, but since the --move doesn't change the structure of mounts underneath the moved mountpoint, I wouldn't expect any changes to be propagated from it to other mountpoints. I must be missing something fundamental.... --Bruce Fields