zero.
Very interesting concept... So you are saying that if I took an additional
reference to the file object during MJ_CLOSE, and then dereferenced it
somewhen later, I would get another MJ_CLOSE?
If you meant the reference count of the last handle (which I highly doubt,
sorry), then what does your remark have to do with the discussion about
FILE_OBJECT?
Right... Let's see what DDK says.
http://msdn.microsoft.com/library/d..._b0a0adfc-46dc-4da2-aed2-826a0b46d00a.xml.asp
IRP_MJ_CLEANUP (***cleaning up***)
When Sent: Receipt of this request indicates that the last handle for a
file
object that is associated with the target device object has been closed
(but, due to outstanding I/O requests, ****might not have been
released***).
http://msdn.microsoft.com/library/d..._bb864c28-6a78-4158-be96-f03e6e23dc74.xml.asp
IRP_MJ_CLOSE (***closing***)
When Sent: Receipt of this request indicates that ***the last handle*** of
the file object that is associated with the target device object ****has
been closed and released***. All outstanding I/O requests have been
completed or canceled.
I seem to be the only one among the contributors to this thread who
understands the concept of FILE_OBJECT reference counters