On 2011-01-18, at 08:50, Lukas Czerner wrote: > +Table of Ext4 specific ioctls > +.............................................................................. > + Ioctl Description > + EXT4_IOC_GETFLAGS Get additional attributes associated with files > + in Ext4. The argument point to the integer. > + Meaning of the particular bits are defined in > + fs/ext4/ext4. This is actually the same value as the FS_IOC_GETFLAGS ioctl. > + EXT4_IOC_SETFLAGS Set additional attributes associated with files > + in Ext4. The argument point to the integer. > + Meaning of the particular bits are defined in > + fs/ext4/ext4. If the file is a subject to quota, > + setting inode flags is prohibited. Likewise, this is the same value as FS_IOC_SETFLAGS. > + EXT4_IOC_GETVERSION > + EXT4_IOC_GETVERSION_OLD > + Get the inode i_generation number stored for > + each inode. This is particularly useful for > + NFS in cases when one inode is unlinked and > + then a new inode is created with the same inode > + number. NFS daemon should know that it is not > + the same inode, thus i_generation is needed. > + All that said, it is normally changed only when > + new inode is created. Similarly, the FS_IOC_GETVERSION matches EXT4_IOC_GETVERSION_OLD. Sadly, the move of this ioctl number to FS_IOC_GETVERSION used the old 'v' ioctl number that conflicts with a number of ioctls instead of the new 'f' ioctl number... Cheers, Andreas -- 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