Re: [PATCH 4/5] ext4: add isolated project support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Hi,

> 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.
  Just a curious question:
Do you really need this subtree separation in your envisioned containers
usecase? Because there I imagine you have one project_id per container,
containers form disjoint subtrees (at least their writeable parts) and
each file & directory has this project_id set and you forbid to manipulate
project id's from inside the container (otherwise you'd have problems with
enforcing quota limits I guess).

And when project_id is a per-inode property, quota has no problems with it
(is well defined) even without subtree separation. So is this subtree
separation really needed?

								Honza
-- 
Jan Kara <jack@xxxxxxx>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux