Hi, from my user mode app I call FilterConnectCommunicationPort only a single time.
In the minifilter code my ConnectNotifyCallback for the communication port gets called two times. I’ve traced the process execution in the debugger and after the callback routine completes the stack unwinds back up to KiFastCallEntry. Then it winds back down until the callback is entered again.
This causes the problem that since there is a maximum number of connections available, since it is connecting twice instead of once, I am running out of connections.
Is there any reason why the callback should be entered twice in this manner?
Thanks,
John
This is not an issue that I have seen before. It is most likely an
issue with how you are using the APIs.
Neal Christiansen
Microsoft NTFS Development Lead
This posting is provided “AS IS” with no warranties, and confers no
Rights
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@altiris.com
Sent: Wednesday, January 17, 2007 2:33 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Calling FilterConnectCommunicationPort Causes a Double
Connect
Hi, from my user mode app I call FilterConnectCommunicationPort only a
single time.
In the minifilter code my ConnectNotifyCallback for the communication
port gets called two times. I’ve traced the process execution in the
debugger and after the callback routine completes the stack unwinds back
up to KiFastCallEntry. Then it winds back down until the callback is
entered again.
This causes the problem that since there is a maximum number of
connections available, since it is connecting twice instead of once, I
am running out of connections.
Is there any reason why the callback should be entered twice in this
manner?
Thanks,
John
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com