From: Andi Kleen Subject: Re: [PATCH 17/18] unbindable mounts Date: 13 Nov 2005 04:00:18 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linuxram@us.ibm.com Return-path: Received: from ns.suse.de ([195.135.220.2]:12987 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1751099AbVKMDA3 (ORCPT ); Sat, 12 Nov 2005 22:00:29 -0500 To: Al Viro In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Al Viro writes: > From: Ram Pai > 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)