Hi folks,
Can somebody help explain evict inode functionality? Specifically I’m interested in know how it interacts with the opening of the same file again?
In NFS development, we’ve been seeing a race between reopening of the same file and evict inode code and unable figure out how to prevent such race. When file is opened for the first timed and then closed. As the last reference is dropped and iput_final() calls evict() which will call filesystem specific evict_inode() code. As that’s happening a new open for the same file is happening and causes problems.
Also can somebody suggest how to debug VFS code, as putting printks generates output for the local filesystem code as well.
Thank you.
(I don’t subscribe to the mailing list please CC in the reply).
��.n��������+%������w��{.n�����{���)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
