FsRtlAreThereCurrentFileLocks returns TRUE if any byte-range locks have been granted for the file, FALSE otherwise.
File systems and filter drivers often call FsRtlAreThereCurrentFileLocks from their FastIoCheckIfPossible routines.
Note If a byte-range lock has existed since the specified file was opened, the FsRtlAreThereCurrentFileLocks routine returns TRUE, unless the relevant FILE_LOCK is reinitialized. If a lock was established, and then released, the use of FsRtlAreThereCurrentFileLocks can prevent the assignment of oplocks unnecessarily. Use FsRtlAreThereCurrentOrInProgressFileLocks to avoid this problem.