Hello,
I encountered an interesting problem while debugging a legacy layered FSFD on Windows 7. When the FSFD passes a paging write request from the mapped page writer to the underlying NTFS driver, the NTFS driver first checks whether the resources of the corresponding file (both the main resource and the paging resource in the file’s FCB header) are acquired. When the NTFS driver finds out none of them is acuired, it acquires the paging resource for shared access. The paging resource is then never released by the NTFS driver and is held indefinitelly.
The question is: Why does the NTFS driver do such thing? I don’t understand what is the reason of this behaviour.
Thank you in advance and have a nice day.
Lenka