Hi,
On Tue, 2006-04-25 at 11:26 +0100, Christoph Hellwig wrote:
> 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?
>
Thats basically what I was proposing with iflags.h, if you think it
would be better renamed to fflags.h and s/IFLAG/FFLAG/g then I'll do
that.
Perhaps I should "dig this out" from the GFS2 code and submit it as a
separate patch.... ?
XFS appears to support the immutable, append, no atime, no dump and sync
flags only, judging by the test in the xfs ioctl code, I don't see any
extra flags:
if (flags & ~(LINUX_XFLAG_IMMUTABLE | LINUX_XFLAG_APPEND | \
LINUX_XFLAG_NOATIME | LINUX_XFLAG_NODUMP | \
LINUX_XFLAG_SYNC)) {
error = -EOPNOTSUPP;
break;
}
Reiserfs appears to use sync, immutable, no tail, append and no atime.
jfs uses No atime, dirsync, sync, secrm, unrm, append and immutable.
So far as I can tell my list already includes all the currently used
flags,
Steve.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
