want to ensure CloseFile is called about dokan HOT 6 OPEN

from Dokan readme
--
Cleanup is invoked when the function CloseHandle in Windows API is executed. If 
the 
file system application stored file handle in the Context variable when the 
function 
CreateFile is invoked, this should be closed in the Cleanup function, not in 
CloseFile function. If the user application calls CloseHandle and subsequently 
open 
the same file, the CloseFile function of the file system application may not be 
invoked before the CreateFile API is called. This may cause sharing violation 
error. 
Note: when user uses memory mapped file, WriteFile or ReadFile function may be 
invoked after Cleanup in order to complete the I/O operations. The file system 
application should also properly work in this case.

It's a bit confusing before you read up on Close and CleanUp. Shouldn't this be
hidden from the user? To do a FUSE API compatible it will have to be anyway. I'm
still looking for a way to force Windows to remove the file from it's cache to 
truly
release it. 

Some of the file systems on http://www.acc.umu.se/~bosse/ only implement
IRP_MJ_CLOSE, but that doesn't strike me as a good solution as it could be a 
long
time after all the handles are closed before IRP_MJ_CLOSE is called.

I see CcFlushCache, CcPurgeCacheSection and CcUninitializeCacheMap are already 
called
after IRP_MJ_CLEANUP has completed, and I would have expected this functions to 
force
Windows' caching to let go over all references to the file so IRP_MJ_CLOSE is 
called.
But looks like this isn't happening, so there must be more to forcing Windows 
to let
go....

I agree with you. CreateFile and Cleanup are confusing.
I found a bug relating CloseFile and fixed it onDokan library 0.3.9. I think 
CloseFile is certainly called.
If you find an example that CloseFile is never called, please let me know.
I might miss something on cache manager.

It seems now the CloseFile should be called instead of cleanup to deal with both
memory mapped files and regular files. I noticed when closing my context in
Cleanup(), the Dokan lib will cause ReadFile to be sent after cleanup() but 
before
CloseFile(). That would cause error in REadFile as handle was no longer valid. I
shifted my cleanup code to CloseFile and it appears to work! So perhaps the docs
should be changed to indicate that Cleanup() is no longer necessary ?

I've gotten the same thing with ReadFile after cleanup.  It's not intuitive 
what to 
do here for the filesystem implementor.  The 'Mirror' example shows that you 
should 
re-open the file and read again.  This doesn't seem right.  How do you know how 
to 
re-open the file with the same permissisons as the original CreateFile?

So, all of my handle closing happens in Cleanup, and my CloseFile does 
virtually 
nothing!