Re[2]: COW file isolation model

NTFSD
1

Yes, but as owner of the upper FO you need to manage all of that. Hence
the complexities of a layered FS.

Pete

Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

------ Original Message ------
From: xxxxx@yahoo.es
To: “Windows File Systems Devs Interest List”
Sent: 3/21/2017 1:59:21 PM
Subject: RE:[ntfsd] COW file isolation model

>But even if I take ownership of the top FO and redirect by myself to
>the corresponding FO depending the type of operation, each FO would end
>up having It’s offset (and probably other fields) updated separatelly
>and that could also cause inconsistencies, isn’t that right?
>
>—
>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:>

2

Thanks Peter. I think I will have to look other methods, because I have the requisite that my driver should be unloadable.

BTW: if I take 2 FO’s managed by the FS, both of them representing the same physical file, but with diferent fscontext2 (different handles), is it possible to “clone” some information from one FOs context2 to the other one? Data like current offset and the like, so that I could make both user handles interchangeable? FltGetfileInfo + FltSetFileInfo… dunno…

Thanks again for your comments, regarding your comment con layered FS I’m looking dokan proyect sources.