On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote: > Project id's are not exactly "subtree" semantic, but inheritance semantics, > which is not the same when non empty directories get their project id changed. > Here is a recap: > https://lwn.net/Articles/623835/ Yes - but if we abuse them for containers we could refine the semantics to simply not allow change of project ids from inside containers based on say capabilities. > I guess we should define the semantics for the required sub-tree marking, > before we can talk about solutions. Good plan.
