NateD-MSFT 9470a99092 Add KeGetCurrentProcessorNumberEx to CQE-457 whitelist ...

Windows driver developers may call KeGetCurrentProcessorNumberEx in their driver.  This function optionally may initialize a provided structure, but this initialization always occurs.  The return value is the current processor being run on.  As such, this query incorrectly marks calls to KeGetCurrentProcessorNumberEx that initialize a structure that is later used as risky, even though in reality the initialization always succeeds.

See https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddk/nf-ntddk-kegetcurrentprocessornumberex

2021-02-04 13:32:09 -08:00

..

examples

C++: Rename Block -> BlockStmt

2020-09-08 08:40:20 +02:00

src

Add KeGetCurrentProcessorNumberEx to CQE-457 whitelist

2021-02-04 13:32:09 -08:00

test

Merge pull request #5094 from MathiasVP/promote-UnsignedDifferenceExpressionComparedZero

2021-02-04 16:54:45 +00:00