From: Arnd Bergmann Subject: Re: [PATCH 00/32] VFS based Union Mount (V3) Date: Tue, 19 May 2009 14:21:20 +0200 Message-ID: <200905191421.21026.arnd@arndb.de> References: <1242662968-11684-1-git-send-email-jblunck@suse.de> <200905191354.08701.arnd@arndb.de> <20090519121504.GO16526@bolzano.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Miklos Szeredi , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, bharata@in.ibm.com, dwmw2@infradead.org, mszeredi@suse.cz, vaurora@redhat.com To: Jan Blunck Return-path: Received: from moutng.kundenserver.de ([212.227.126.177]:54681 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751190AbZESMWH (ORCPT ); Tue, 19 May 2009 08:22:07 -0400 In-Reply-To: <20090519121504.GO16526@bolzano.suse.de> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tuesday 19 May 2009, Jan Blunck wrote: > On Tue, May 19, Arnd Bergmann wrote: > > This would work, but you'd have to do this for each file system if you want > > to be able to use it as the top of the union while backed by a read-only > > block device or when you don't want it to be written. > > I know that the requirement for the topmost filesystem to be able to create > directories and fill them with fallthrus is an unattractive one. On the other > hand this is the cost that you have to pay at the moment to get this kind of > functionality. This implementation will not help with all use-cases. Its focus > is to get certain use-cases right. So what would go wrong if you only made them persistent for writable file systems, but allowed fallthrough dentries to be discarded for read-only file systems? As long as the lower layers don't change, you should still be able to reconstruct the same dentries every time you do a readdir, right? Arnd <><