As long as the SOPs for the upper and lower FOs are different, then
you’ll simply end up with 2 sections. That said, in general, you would
like to avoid having caching initialized on the lower FO unless you want
to also control direct access to that file, which you should be anyway.
But again, there are design dependencies here.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com http:</http:>
866.263.9295
------ Original Message ------
From: xxxxx@mauroleggieri.com.ar
To: “Windows File Systems Devs Interest List”
Sent: 4/18/2016 6:05:24 PM
Subject: RE:[ntfsd] Re[2]: Official way to hook GetMappedFileNameW in
kernel?
>Thanks again Peter, I’ll study that option.
>
>If I call CcInitializeCacheMap with the upper FO and update data in
>lower FO, a later call to CcInitializeCacheMap with the lower FO issued
>by the ntfs/fat driver won’t generate a conflict?
>
>Regards,
>Mauro.
>
>—
>NTFSD is sponsored by OSR
>
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:</http:></http:>