|
FastIoAcquireFileExclusive
|
| bet | 6/9 | | Sana | 22.07.2021 | | Hajmi | 124 Kb. | | #15612 |
FastIoAcquireFileExclusive
FastIoReleaseFile
FastIoAcquireFileForCcFlush
FastIoReleaseFileForCcFlush
FastIoAcquireFileForModWrite
FastIoReleaseFileForModWrite
The filters in the file system filter stack were skipped in these calls because the system could not tolerate the filter not passing the operation down to the base file system. To solve this problem, the filter team has come up with a new way for file system filters to register for callbacks for these operations in such a way that we can now ensure that the operation is getting to the base file system.
To register these callbacks, filters should call FsRtlRegisterFileSystemFilterCallbacks. This new interface has two key benefits:
Currently, the filter driver writer community has developed a number of very ugly hacks so that they can see these operations occurring. The hacks usually severely limit the interoperability between filters. The new interface provides a safe mechanism that enables filter drivers to see these operations, so these hacks are longer needed.
In the past, even if a filter could find some way to get notified of these operations, there was no way that the filter could fail the FastIoAcquireFileExclusive operation (in rare cases, this is needed by HSM's filter). Now, filters have the ability to fail acquire operations and these failures will be passed back to the originator of the operation.
|
| |
