Mark Fasheh: > The following patches fix these inconsistencies by introducing a VFS helper > function which calls the underlying filesystem ->getattr to get our real > inode number / device pair. The returned values can then be used at those > places in the kernel where we are incorrectly reporting our ino/dev pair. > We then update fs/proc/ and fs/locks.c to use this helper when writing to > /proc/PID/maps and /proc/locks respectively.
I definitly agree that ino/dev pair should be a unique identity on the system. But I don't know why you are tryng to solve the problem in generic VFS layer instead of the problematic FS. Isn't it an unnecessary overhead for many FS? How about creating a new f_op member ->get_ino_dev(), ->show_identity() or something, and implement the new f_op in the problematic FS only? I hope it will be a lighter way to get the pair than generic getattr way. J. R. Okajima -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
