Dear ext2 maintainers I have a question of inode's i_size. I found that it is hard to find any consistent synchronization mechanism that protects inode's i_size field. Is there any lock or synchronization mechanism that consistently protects i_size fields of inode objects to avoid data race? In inode's definition in /include/linux/fs.h, there is comment that i_lock protects i_size but it is not clear. Sincerely Shin Hong -- 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
