From: Andreas Gruenbacher Subject: Re: [PATCH 6/7 v3] overlay: hybrid overlay filesystem prototype Date: Mon, 27 Sep 2010 13:49:48 +0200 Message-ID: <201009271349.49077.agruen@suse.de> References: <20100920180404.939991832@szeredi.hu> <20100924175653.GB25129@shell> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Cc: Valerie Aurora , linuxram@us.ibm.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, neilb@suse.de, viro@zeniv.linux.org.uk To: Miklos Szeredi Return-path: Received: from cantor.suse.de ([195.135.220.2]:52934 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751374Ab0I0Ltw (ORCPT ); Mon, 27 Sep 2010 07:49:52 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Monday 27 September 2010 10:11:53 Miklos Szeredi wrote: > [...] marking new directories opaque is only a half solution. > E.g. consider the case when we have /a/b/c/ on the lower fs > and /a/b/ on the upper, which is not opaque. Then /a/b/c/ is created > on the upper fs off-line. The union logic can't notice that "c" > should really be opaque and will merge with the contents of the lower > layer. I can think of arguments for either behavior, perhaps with a slight preference for your suggestion (default = opaque). In any case, admins will need a way to flip opaque flags and remove undesired whiteouts. Thanks, Andreas