Partager via

FilterOidRequest (Compact 7)

  • Article

3/12/2014

NDIS calls a filter driver's FilterOidRequest function to process an OID request that is associated with the specified filter module.

Syntax

NDIS_STATUS
  FilterOidRequest(
    IN NDIS_HANDLE  FilterModuleContext,
    IN PNDIS_OID_REQUEST  OidRequest
    );

Parameters

  • FilterModuleContext
    A handle to the context area for the filter module that is the target of this request. The filter driver created and initialized this context area in the FilterAttach function.
  • OidRequest
    A pointer to an NDIS_OID_REQUEST structure that specifies the operation requested including the OID_XXX code. The structure can specify either a query request or a set request. For more information about OIDs, see NDIS OIDs.

Return Value

FilterOidRequest returns one of the following status values:

Value Description

NDIS_STATUS_SUCCESS

FilterOidRequest successfully completed the filter driver's query or set operation for this filter module.

NDIS_STATUS_PENDING

Indicates that the filter driver will complete the request asynchronously. After the driver is complete the request, it must call the NdisFOidRequestComplete function to inform NDIS that the request is complete.

NDIS_STATUS_INVALID_OID

Indicates that the request, specified at OidRequest, is invalid or not recognized.

NDIS_STATUS_NOT_SUPPORTED

FilterOidRequest does not support the OID, the OID is optional.

NDIS_STATUS_BUFFER_TOO_SHORT

Indicates that the buffer, supplied at OidRequest, is too small to hold the requested data.

NDIS_STATUS_INVALID_LENGTH

For a query operation, the InformationBufferLength member of the NDIS_OID_REQUEST structure does not match the length required by the given OID. FilterOidRequest returned the required buffer size, in bytes, in the BytesNeeded member of the NDIS_OID_REQUEST structure.

NDIS_STATUS_INVALID_DATA

For a set operation, the data supplied in the InformationBuffer member of the NDIS_OID_REQUEST structure was invalid for the given OID.

NDIS_STATUS_NOT_ACCEPTED

FilterOidRequest attempted to collect the requested information but was unsuccessful.

NDIS_STATUS_RESOURCES

FilterOidRequest failed because of insufficient resources.

NDIS_STATUS_FAILURE

FilterOidRequest returns NDIS_STATUS_FAILURE if none of the preceding values applies. The filter driver should call the NdisWriteErrorLogEntry function that has parameters that specify the reason for the failure.

Remarks

FilterOidRequest is an optional function. If a filter driver does not use OID requests, it can set the entry point for this function to NULL when it calls the NdisFRegisterFilterDriver function. If a filter driver defines a FilterOidRequestComplete function, it must provide the FilterOidRequest function.

NDIS calls the filter driver's FilterOidRequest function to process OID requests that are originated by overlying drivers. Filter drivers can forward such requests to underlying drivers by calling the NdisFOidRequest function.

Before the driver calls NdisFOidRequest, the driver must allocate an NDIS_OID_REQUEST structure and transfer the request information to the new structure by calling NdisAllocateCloneOidRequest. As an option, a filter driver can complete a request immediately without forwarding the request.

To complete a request synchronously, the filter driver returns NDIS_STATUS_SUCCESS or a failure status. If the driver returns NDIS_STATUS_PENDING, it must call the NdisFOidRequestComplete function to inform NDIS that the request is complete.

For a query operation, FilterOidRequest returns the requested information in the InformationBuffer member and sets the variable in the BytesWritten member of the NDIS_OID_REQUEST structure to the amount of information that it returned. The underlying drivers do this if the filter driver passed the request on with NdisFOidRequest.

For a set operation, FilterOidRequest can use the data in the InformationBuffer member of the NDIS_OID_REQUEST structure to set the information that is required by the given OID. In this case, FilterOidRequest sets the variable at BytesRead to the amount of the supplied data that it used. The underlying drivers do this if the filter driver passed the request on with NdisFOidRequest.

Like miniport drivers, filter drivers can receive only one request at a time. NDIS serializes requests that it sends to a filter driver. NDIS cannot call FilterOidRequest before a filter driver completes the current request.

NDIS calls FilterOidRequest at IRQL <= DISPATCH_LEVEL.

Requirements

Header

filter.h

See Also

Reference

NDIS OID Request Interface for Filter Drivers
FilterAttach
NDIS_OID_REQUEST
NdisAllocateCloneOidRequest
NdisFOidRequest
NdisFOidRequestComplete
NdisWriteErrorLogEntry