From: Christoph Hellwig Subject: Re: [PATCH 05/16] GFS2: File and inode operations Date: Tue, 25 Apr 2006 11:26:28 +0100 Message-ID: <20060425102628.GA26219@infradead.org> References: <1145636030.3856.102.camel@quoit.chygwyn.com> <20060423075525.GP6075@schatzie.adilger.int> <1145886796.3856.161.camel@quoit.chygwyn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andreas Dilger , Andrew Morton , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:36500 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S932179AbWDYK0d (ORCPT ); Tue, 25 Apr 2006 06:26:33 -0400 To: Steven Whitehouse Content-Disposition: inline In-Reply-To: <1145886796.3856.161.camel@quoit.chygwyn.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Apr 24, 2006 at 02:53:16PM +0100, Steven Whitehouse wrote: > > Actually, the 0x0080000 flag has been reserved by e2fsprogs for ext3 > > extents for a while already. AFAICS, there are no other flags in the > > current e2fsprogs that aren't listed above. > > > So if I call that one IFLAG_EXTENT, then I presume that will be ok? > What about the 0x00040000 flag? That would seem to be a gap in the > sequence (ignoring GFS flags for now), so should I leave that reserved > for use by ext2/3 as well? note that at least reiserfs, jfs snd xfs seem to use additional flags aswell. It would be really helpful if we could get a linux/fflags.h that collects all of having them spread all over. Anyone volunteering to create it?