Re: [PATCH v3 2/5] fat: allocate persistent inode numbers

[OGAWA Hirofumi]

OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx> writes:

> Namjae Jeon <linkinjeon@xxxxxxxxx> writes:
>
>>> What is problem if i_ino + i_generation is not match? I think, even if
>>> those didn't match, i_pos in FH should resolve issue, no?
>> No, It can not resolve issue.
>> in NFS file handle, there is a reference to the current inode number.
>> So, if by eviction that is changed - that it will results in "file id
>> changed" error.
>
> Who returns error?

This means - which code returns error?

>> even though using the i_pos we can reconstruct and get the INODE on
>> the Server, but the NFS handle is no more valid. As the inode number
>> is also changed, iunique() for the file will result in different
>> number this time.

-- 
OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/