On Mon, 2011-07-11 at 15:36 +0200, Michal Suchanek wrote: > On 11 July 2011 14:00, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > On Mon, 2011-07-11 at 12:01 +0100, David Howells wrote: > >> Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > >> > > >> > Also, why would you want to have a class per sb-instance? From last > >> > talking to David, he said there could only ever be 2 filesystems > >> > involved in this, the top and bottom, and it is determined on (union) > >> > mount time which is which. > >> > >> There can be more than 2 - one upperfs (the actual union) and many lowerfs - > >> though I think only one lowerfs is accessed at a time. > > > > Right, however I understood from our earlier discussion that the vfs > > would only ever try to lock 2 filesystems at a time, the top and one > > lower. > > This is true from local point of view. However, it is technically > possible to use overlayfs as the upper layer of another overlayfs > which allows layering multiple readonly "branches" into a single > overlay. Since the vfs will lock the "union" and one (or possibly > both) of its branches and one of the branches may be itself an union > you can get arbitrary depth (which is currently limited by a constant > in the code to cut recursion depth and stack usage). Off topic but can you elaborate on that? Are you saying the "unioned stack" can consist of more than two file systems and can have more than two layers and possibly a mix of multiple read-only and read-write file systems? Ian -- 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
