From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. R. Okajima" Subject: Re: [PATCH 0/7] overlay filesystem: request for inclusion Date: Mon, 20 Jun 2011 09:43:48 +0900 Message-ID: <6167.1308530628@jrobl> References: <20110609125114.8dff08da.akpm@linux-foundation.org> <20110610100143.28037551@lxorguk.ukuu.org.uk> <8739jbjqa7.fsf@tucsk.pomaz.szeredi.hu> <11186.1308148376@jrobl> <87vcw7hz7y.fsf@tucsk.pomaz.szeredi.hu> <15402.1308154495@jrobl> <18273.1308192226@jrobl> <12737.1308237353@jrobl> Cc: Miklos Szeredi , Alan Cox , Valerie Aurora , Andrew Morton , NeilBrown , viro@zeniv.linux.org.uk, torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, apw@canonical.com, nbd@openwrt.org, jordipujolp@gmail.com, ezk@fsl.cs.sunysb.edu To: Michal Suchanek Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Michal Suchanek: > Is there any reason why a directory cannot be whiteout? Just to reduce consuming inodes. > It may possibly hide a XXXXXXXX file if it is later added to the lower layer. No, because it is "doubly" whiteouted. > Just as whiteout has totally different file-type from a file. It's > specific to the union. Ok, we are talking about different whiteouts. J. R. Okajima