Microsoft is aware of an issue with ExAllocatePoolPriorityZero that can lead to an allocation not getting zeroed on Windows 10, version 1909. We recommend not using ExAllocatePoolPriorityZero for drivers targeting Windows 10, version 1909. This warning will be removed when the issue is fixed.
This routine is a wrapper for and a recommended replacement option for ExAllocatePoolWithTagPriority.
ExAllocatePoolPriorityZero allocates pool memory of the specified type.
PVOID ExAllocatePoolPriorityZero( __drv_strictTypeMatch(__drv_typeExpr)POOL_TYPE PoolType, SIZE_T NumberOfBytes, ULONG Tag, EX_POOL_PRIORITY Priority );
The type of pool memory to allocate. For a description of the available pool memory types, see POOL_TYPE.
You can modify the enumeration value by performing a bitwise-OR with the POOL_RAISE_IF_ALLOCATION_FAILURE flag defined in
wdm.h. This flag causes an exception to be raised if the request cannot be satisfied. Use of this flag is not recommended because it is costly.
Similarly, you can modify the PoolType value by bitwise-ORing this value with the POOL_COLD_ALLOCATION flag (also defined in
wdm.h) as a hint to the kernel to allocate the memory from pages that are likely to be paged out quickly. To reduce the amount of resident pool memory as much as possible, you should not reference these allocations frequently. The POOL_COLD_ALLOCATION flag is only advisory.
The number of bytes to allocate.
The pool tag to use for the allocated memory. Specify the pool tag as a non-zero character literal of one to four characters delimited by single quotation marks (for example,
Tag1). The string is usually specified in reverse order (for example,
1gaT). Each ASCII character in the tag must be a value in the range 0x20 (space) to 0x7E (tilde). Each allocation code path should use a unique pool tag to help debuggers and verifiers identify the code path.
An EX_POOL_PRIORITY enumeration value specifying the priority of this request.
ExAllocatePoolPriorityZero returns NULL if there is insufficient memory in the free pool to satisfy the request unless POOL_RAISE_IF_ALLOCATION_FAILURE is specified. Otherwise, the routine returns a pointer to the allocated memory.
To run on versions of Windows prior to Windows 10 version 2004, the driver must define POOL_ZERO_DOWN_LEVEL_SUPPORT and call ExInitializeDriverRuntime before calling this function.
See the Remarks section of ExAllocatePoolWithTagPriority for additional guidance.
|Minimum supported client||Requires WDK for Windows 10, version 2004. Targets Windows 7 and later versions of the Windows operating system.|
|Header||wdm.h (include Wdm.h, Ntddk.h, Ntifs.h)|
|IRQL||<= DISPATCH_LEVEL (see Remarks section)|
|DDI compliance rules||IrqlExAllocatePool, IrqlExFree2, HwStorPortProhibitedDDIs, SpNoWait, StorPortStartIo|