The FsRtlOplockFsctrlEx routine performs various opportunistic lock (oplock) operations on behalf of a file system or filter driver.
NTSTATUS FsRtlOplockFsctrlEx( POPLOCK Oplock, PIRP Irp, ULONG OpenCount, ULONG Flags );
An opaque oplock pointer for the file. This pointer must have been initialized by a previous call to FsRtlInitializeOplock.
A pointer to the IRP for the I/O operation. This parameter is required and cannot be NULL.
Number of user handles for the file, if an exclusive oplock is being requested. Setting a nonzero value for a level 2, R, or RH oplock request indicates that there are byte-range locks on the file. For information about oplock types, see Oplock Semantics Overview.
A bitmask for the associated oplock operations. A file system or filter driver sets bits to specify the behavior of FsRtlOplockFsctrlEx. The Flags parameter has the following options:
Specifies that the file system verified that all oplock keys on any currently open handles match. By specifying this flag, you allow the oplock package to grant an oplock of level RW or RWH when more than one open handle to the file exists. For more information about oplock types, see the Oplock Semantics Overview page.
FsRtlOplockFsctrlEx returns one of the following NTSTATUS values:
||For an IRP_MJ_CREATE request, STATUS_SUCCESS indicates that the requested filter opportunistic lock (oplock) was granted. For a FSCTL operation, the meaning of STATUS_SUCCESS depends on the FSCTL code. For more information, see the reference pages for the FSCTL codes that are listed in the following Remarks section.|
||The I/O operation was canceled. STATUS_CANCELLED is an error code.|
||The FSCTL code for the I/O operation was not one of the valid values listed in the following Remarks section. STATUS_INVALID_PARAMETER is an error code.|
||The oplock could not be granted. STATUS_OPLOCK_NOT_GRANTED is an error code.|
||Used only for FSCTL operations. The meaning of STATUS_PENDING depends on the FSCTL code. For more information, see the reference pages for the FSCTL codes that are listed in the following Remarks section. STATUS_PENDING is a success code.|
File systems and filter drivers call FsRtlOplockFsctrlEx to perform various opportunistic lock operations for a create operation or file system control I/O operation. The IRP pointed to by the Irp parameter must be a valid IRP for an IRP_MJ_FILE_SYSTEM_CONTROL or IRP_MJ_CREATE operation.
If the IRP is an IRP_MJ_FILE_SYSTEM_CONTROL request, FsRtlOplockFsctrlEx can be used with the following FSCTL codes. The FSCTL code is set in IrpSp->Parameters.FileSystemControl.FsControlCode. For more information about file system control parameters, see the reference entry for IRP_MJ_FILE_SYSTEM_CONTROL.
For more information about these FSCTLs and about opportunistic locks in general, see the Microsoft Windows SDK documentation.
If the IRP is an IRP_MJ_CREATE request, FsRtlOplockFsctrlEx can be used to request a pending filter opportunistic lock (oplock) if all of the following conditions are true:
- The value of the OpenCount parameter must be 1.
- The value of the DesiredAccess parameter for the IRP_MJ_CREATE request must be FILE_READ_ATTRIBUTES.
- The value of the ShareAccess parameter for the IRP_MJ_CREATE request must be FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE.
Minifilters should call FltOplockFsctrlEx instead of FsRtlOplockFsctrlEx.
|Minimum supported client||The FsRtlOplockFsctrlEx routine is available starting with Windows 7.|
|Header||ntifs.h (include Ntifs.h)|