On Thu, 2009-07-23 at 15:37 -0500, Eric Sandeen wrote: > I'm confused (again?) :). I don't see FS_FALLOC_FL in the latest kernel > source, and ext2 (well, my ext2 anyway) can't do fallocate(). Google > (well, my google search) can't find it either. Is this something in > your tree? No, I'm the one who got confused, yes, that's part of a hack in our tree. You did answer my question, though, at least partly: > As for: > > #define EXT4_EXT_MIGRATE 0x00100000 /* Inode is migrating */ > > this is not in the mask that FS_IOC_GETFLAGS can see ... and I don't > think anyone else uses FS_DIRECTIO_FL. > > I'm not sure if the flags not in FS_FL_USER_VISIBLE are supposed to be > fs-unique. The flag will need to be generic in any case, since inode_setattr() has to look at it when it's deciding whether or not to call vmtruncate(). Other filesystems that properly implement fallocate() may want to use it for this purpose as well. -- Frank Mayhar <fmayhar@xxxxxxxxxx> Google, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
