Hi, For a while now, I've been annoyed by the fact that function iget_locked and friends (test_inode_iunique, find_inode_fast, ilookup, etc.) use "unsigned long ino" rather than u64 for inode number. File systems need to be consistent across multiple architectures, and 32-bits is hardly adequate for modern storage. This can only result in problems and/or unnecessary restrictions for file systems with block-number based inode numbers like gfs2, and/or force them to kludge around it to prevent problems in mixed architectures. (Not that anyone is likely to use GFS2 on a 32-bit arch, but still.) Opinions? Regards, Bob Peterson Red Hat File Systems -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
