From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Blunck" <jblunck@suse.de>
Subject: Re: [RFC][PATCH 3/14] Add the whiteout file type
Date: Tue, 15 May 2007 08:00:10 +0200
Message-ID: <4de7f8a60705142300h342f5afaxfcc3aa292949f8f4@mail.gmail.com>
References: <20070514093722.GB4139@in.ibm.com>
	 <20070514093943.GE4139@in.ibm.com>
	 <Pine.LNX.4.61.0705142239290.9570@yvahk01.tjqt.qr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Bharata B Rao" <bharata@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	"Jan Blunck" <j.blunck@tu-harburg.de>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from an-out-0708.google.com ([209.85.132.245]:25038 "EHLO
	an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1758196AbXEOGAL (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 15 May 2007 02:00:11 -0400
Received: by an-out-0708.google.com with SMTP id d18so483877and
        for <linux-fsdevel@vger.kernel.org>; Mon, 14 May 2007 23:00:11 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.61.0705142239290.9570@yvahk01.tjqt.qr>
Content-Disposition: inline
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On 5/14/07, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
> On May 14 2007 15:09, Bharata B Rao wrote:
> >
> >A white-out stops the VFS from further lookups of the white-outs name and
> >returns -ENOENT. This is the same behaviour as if the filename isn't
> >found. This can be used in combination with union mounts to virtually
> >delete (white-out) files by creating a file with this file type.
> >
> >Signed-off-by: Jan Blunck <j.blunck@tu-harburg.de>
> >Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> >---
> > include/linux/stat.h |    2 ++
> > 1 files changed, 2 insertions(+)
> >
> >--- a/include/linux/stat.h
> >+++ b/include/linux/stat.h
> >@@ -10,6 +10,7 @@
> > #if defined(__KERNEL__) || !defined(__GLIBC__) || (__GLIBC__ < 2)
> >
> > #define S_IFMT  00170000
> >+#define S_IFWHT  0160000      /* whiteout */
> > #define S_IFSOCK 0140000
> > #define S_IFLNK        0120000
> > #define S_IFREG  0100000
>
> I wonder why 110000, 130000 or 150000 could not also be used?
>

I used the S_IFWHT definition like it is referenced in stat(2). I
guess it would be a good idea to use the same flag on BSD and Linux.

As you can see in stat(2) other OS use 011, 013 and 015.