Fix Compiler Warnings & Migrate to ExAllocatePool2 |WDK 10 #384
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses compiler warnings detected during the build process and replaces deprecated memory allocation API calls with ExAllocatePool2. The changes ensure compatibility with newer Windows Driver Kit (WDK) versions and improve memory allocation safety.
Changes
Fixed compiler warnings identified by static analysis and build checks.
Replaced occurrences of ExAllocatePoolWithTag with ExAllocatePool2 for improved security and future compatibility.
Updated relevant headers and ensured proper flag usage for ExAllocatePool2.
Verified successful build and tested basic memory allocation scenarios.
Rationale
Microsoft recommends using ExAllocatePool2 as it provides better security and control over memory allocations. The new API supports additional flags that enhance robustness and prevent potential vulnerabilities.
Testing
Successfully compiled with the latest WDK without warnings.
Verified correct allocation and deallocation behavior in a test driver.
Ensured that all modified code paths function as expected.