Messages in this thread | | | From | OGAWA Hirofumi <> | Subject | Re: [PATCH v3 2/5] fat: allocate persistent inode numbers | Date | Mon, 24 Sep 2012 15:36:27 +0900 |
| |
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
> Namjae Jeon <linkinjeon@gmail.com> 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@mail.parknet.co.jp>
| |