[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141114095511.789a76ac@gmail.com>
Date: Fri, 14 Nov 2014 09:55:11 +0100
From: Jordi Pujol Palomer <jordipujolp@...il.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: linux-unionfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, David Howells <dhowells@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>, "A. Wan" <jm@...wan.com>,
Patrick Frisch <patrick@...schux.de>,
Aaron Campbell <aaron@...or.net>
Subject: Re: [RFC PATCH] overlayfs: support more than one read-only layer
EL Mon, 10 Nov 2014 10:09:54 +0100
Miklos Szeredi <miklos@...redi.hu> escrigué:
> Maybe it wasn't clear, but the number of lower layers isn't limited by
> FILESYSTEM_MAX_STACK_DEPTH,
sorry, you have been clear, it's me that have not explained the purpose
of that patch. This idea is also valid for the main overlayfs
development.
Consider that we have an encrypted partition and a live OS that
uses overlayfs and works over it, when the OS is started already
reaches the maximum stacking depth (2). Also, hardcoding parameters
into the code may be annoying because a change implies creating and
mantaining patches, otherwise when the parameter is configurable we can
change it in a config value.
Also, I include a patch to explain better my first statement,
would say lowerdirs has extended the functionality of lowerdir,
therefore we can discard the lowerdir case that only works with one
lower layer and rename lowerdirs to lowerdir. It's more simple and all
the functionality is preserved.
Regards,
Jordi Pujol
View attachment "23-overlayfs_discard_specifically_support_only_one_read-only_layer.patch.txt" of type "text/plain" (2526 bytes)
Powered by blists - more mailing lists