[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100311120747.GD4706@infradead.org>
Date: Thu, 11 Mar 2010 07:07:47 -0500
From: Christoph Hellwig <hch@...radead.org>
To: Dmitry Monakhov <dmonakhov@...nvz.org>
Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 4/5] ext4: add isolated project support
On Thu, Mar 04, 2010 at 09:34:36PM +0300, Dmitry Monakhov wrote:
> PROJECT_ISOLATION
> This feature allows to create an isolated project subtrees.
> Isolation means what:
> 1) directory subtree has no common inodes (no hadlinks across subtrees)
> 2) All descendants belongs to the same subtree.
>
> Project subtree's isolation assumptions:
> 1)Inode can not belongs to different subtree trees
> Otherwise changes in one subtree result in changes in other subtree
> which contradict to isolation criteria.
>
> *Usage*
> We already has bind mounts which prevent link/remount across mounts.
> But if user has isolated project which consists of several subtrees
> and he want link/renames to work between subtrees(but in one project)
>
> Since this feature is non obvious it controlled by mount option.
Making this a mount option is even more non-obvious. Unless you have
very good reason to support both and not just stick to the existing
"isolated" semantics make it a chattr option so we can easily check
out what kind of subtree we deal with.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists