CacheManager Callback routines..

NTFSD
1

Hi,

I am in the process of writing a simple File System Driver. I have a question on the parameters that are passed to the CacheManagerCallback routines. Rajeev Nagar’s book says that the first parameter for say, AcquireForLazyWrite should be a PVOID Context, which is then cast to PCCB. However, the FastFat example says that the parameter is a PVOID Context, which is then cast to PFCB.

Can any one tell me which one is right? It looks like the FastFat source is correct as it is more recent.

Thanks,
Giri

2

It doesn’t matter, it is up to the file system designer. It is YOUR
context, pass whatever you need to.

-Jeff

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Monday, October 22, 2007 9:22 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] CacheManager Callback routines…

Hi,

I am in the process of writing a simple File System Driver. I have a
question on the parameters that are passed to the CacheManagerCallback
routines. Rajeev Nagar’s book says that the first parameter for say,
AcquireForLazyWrite should be a PVOID Context, which is then cast to
PCCB. However, the FastFat example says that the parameter is a PVOID
Context, which is then cast to PFCB.

Can any one tell me which one is right? It looks like the FastFat source
is correct as it is more recent.

Thanks,
Giri

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@emc.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

… However be careful with the PERESOURCE parameter to AcquireForModWrite
in Vista. They have hijacked some of the bottom three bits for their own
purposes in the assumption that the value *will* be a properly allocated
ERESOURCE…