My driver attaches to Tcp, Udp, Rawip
So I observe that some FileObjects are created and destroyed …
Is it nornal situation, when a FileObject is created and after that in some
time I receive a number of requests to destroy this FileObject ?
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Are you certain that you are observing the same file object? TCP sessions use 2
file objects.
Are you sure that subsequent destroy requests are for the same session? Maybe
the I/O manager is rapidly reusing file objects.
Dave
foxgen wrote:
My driver attaches to Tcp, Udp, Rawip
So I observe that some FileObjects are created and destroyed …Is it nornal situation, when a FileObject is created and after that in some
time I receive a number of requests to destroy this FileObject ?
You are currently subscribed to ntdev as: xxxxx@okena.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Well, I see multiple IRP_MJ_CLOSE coming with the same
pStackLocation->FileObject…
What could this mean ?
Are you certain that you are observing the same file object? TCP sessions
use 2
file objects.
Are you sure that subsequent destroy requests are for the same session?
Maybe
the I/O manager is rapidly reusing file objects.
Dave
foxgen wrote:
My driver attaches to Tcp, Udp, Rawip
So I observe that some FileObjects are created and destroyed …Is it nornal situation, when a FileObject is created and after that in some
time I receive a number of requests to destroy this FileObject ?
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com