From: Christoph Hellwig <hch@infradead.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/16] GFS2: File and inode operations
Date: Tue, 25 Apr 2006 11:26:28 +0100 [thread overview]
Message-ID: <20060425102628.GA26219@infradead.org> (raw)
In-Reply-To: <1145886796.3856.161.camel@quoit.chygwyn.com>
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?
next prev parent reply other threads:[~2006-04-25 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 16:13 [PATCH 05/16] GFS2: File and inode operations Steven Whitehouse
2006-04-23 7:55 ` Andreas Dilger
2006-04-24 13:53 ` Steven Whitehouse
2006-04-24 22:19 ` Andreas Dilger
2006-04-25 9:27 ` Steven Whitehouse
2006-04-25 10:26 ` Christoph Hellwig [this message]
2006-04-25 11:14 ` Steven Whitehouse
2006-04-25 12:38 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060425102628.GA26219@infradead.org \
--to=hch@infradead.org \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).