DUAL_OPLOCK_KEY_ECP_CONTEXT - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntifs.h
typedef struct _DUAL_OPLOCK_KEY_ECP_CONTEXT {
GUID ParentOplockKey;
GUID TargetOplockKey;
BOOLEAN ParentOplockKeySet;
BOOLEAN TargetOplockKeySet;
} DUAL_OPLOCK_KEY_ECP_CONTEXT, *PDUAL_OPLOCK_KEY_ECP_CONTEXT;
View the official Windows Driver Kit DDI referenceNo description available.
The DUAL_OPLOCK_KEY_ECP_CONTEXT structure contains the extra create parameter context for a dual oplock key. Oplocks keys for both a target and a parent file object can be set in this structure.
ParentOplockKeyA GUID representing the parent oplock key value.
TargetOplockKeyA GUID representing the target oplock key value.
ParentOplockKeySetSet to TRUE if ParentOplockKey contains a valid GUID for the parent's oplock key.
TargetOplockKeySetSet to TRUE if TargetOplockKey contains a valid GUID for the target's oplock key.
The DUAL_OPLOCK_KEY_ECP_CONTEXT structure provides dual oplock keys to allow oplock requests on files and directories. Like the OPLOCK_KEY_ECP_CONTEXT structure, DUAL_OPLOCK_KEY_ECP_CONTEXT is set in an extra create parameter list (ECP_LIST) and later associated with a file object during processing of IRP_MJ_CREATE by a file system or file system filter driver.
The value GUID_ECP_DUAL_OPLOCK_KEY is used when calling support routines such as FsRtlAllocateExtraCreateParameter, FsRtlInitializeExtraCreateParameter, or FltRemoveExtraCreateParameter.