From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: [PATCH 0/7 v3] overlay filesystem prototype Date: Tue, 21 Sep 2010 11:31:01 +1000 Message-ID: <20100921113101.3bde59bd@notabene> References: <20100920180404.939991832@szeredi.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, vaurora@redhat.com, viro@zeniv.linux.org.uk To: Miklos Szeredi Return-path: Received: from cantor2.suse.de ([195.135.220.15]:36345 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751391Ab0IUBbM (ORCPT ); Mon, 20 Sep 2010 21:31:12 -0400 In-Reply-To: <20100920180404.939991832@szeredi.hu> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, 20 Sep 2010 20:04:04 +0200 Miklos Szeredi wrote: > Here's an updated patch series. > > For now I reverted Neil's revalidation patch. Not requiring strict > read-only would make sense for just trying it out and experimenting. > But for real uses, I'm not sure... :-) I think you significantly reduce the value by insisting on read-only but as this is purely a theoretical perspective at the moment (I have no concrete use-case) I won't push it. I had another patch I was working on which caused overlayfs to keep negative dentries in upperdentry or lowerdentry rather than just setting them to NULL. This would allow revalidation to notice objects appearing in the underlying filesystem. I guess you won't want that now .... I think it made some of the code a bit neater, but I never finished it so I cannot be sure of the overall effect. I'm curious as to why upperdentry is now called __upperdentry - it isn't clear from a quick reading.. Thanks, NeilBrown