A filter driver must call the NdisFRestartComplete function to complete a restart operation if the driver returned NDIS_STATUS_PENDING from its FilterRestart function.
VOID NdisFRestartComplete( _In_ NDIS_HANDLE NdisFilterHandle, _In_ NDIS_STATUS Status );
The NDIS handle that identifies this filter module. NDIS passed the handle to the filter driver in a call to the FilterAttach function.
The final status of the restart operation. The following status values are supported:
The driver successfully restarted the flow of network data.
The restart failed because of insufficient resources.
The driver indicates NDIS_STATUS_FAILURE if none of the preceding values applies. The driver should call the NdisWriteEventLogEntry function together with parameters that specify the reason for the failure.
NDIS calls a filter driver's FilterRestart function to initiate a restart request for filter module. The filter module remains in the Restarting state until the restart operation is complete.
A pending restart operation is complete after the driver calls the NdisFRestartComplete function. The filter module is in the Running state after the restart operation is complete.
A filter driver can resume indicating received network data immediately after NDIS calls FilterRestart and before the driver calls NdisFRestartComplete. The driver should be ready to accept send requests after it completes the restart operation.
|Windows version||Supported in NDIS 6.0 and later.|
|Header||ndis.h (include Ndis.h)|
|DDI compliance rules||Irql_Filter_Driver_Function|