CDO in Minifilter?

NTFSD Folk:

There is an example of a Control Device Object (CDO) in the Minifilter
directory, but it seems very comprehensive.

I need my CDO to handle one function: IRP_MJ_DEVICE_CONTROL (plus obviously
create/close/cleanup).

Do I need to include *all* the functions listed in the CDO example,
including all the fastio functions? Seems like unnecessary overhead. What
happens to uninitialized entries in the DriverObject->MajorFunction and
DriverObject->FastIoDispatch tables for minifilters?

Thanks,
Ken

Ken,

You do not need to define all of the routines. The sample does this for
completeness (it is easier to remove code from a sample then to add it).

We have an internal minifilter which has a CDO but does not define any
of the fastio routines and it works fine.

Neal Christiansen
Microsoft File System Filter Group 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 Ken Cross
Sent: Monday, October 04, 2004 4:34 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] CDO in Minifilter?

NTFSD Folk:

There is an example of a Control Device Object (CDO) in the Minifilter
directory, but it seems very comprehensive.

I need my CDO to handle one function: IRP_MJ_DEVICE_CONTROL (plus
obviously
create/close/cleanup).

Do I need to include *all* the functions listed in the CDO example,
including all the fastio functions? Seems like unnecessary overhead.
What
happens to uninitialized entries in the DriverObject->MajorFunction and
DriverObject->FastIoDispatch tables for minifilters?

Thanks,
Ken


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