Alex Ionescu wrote:
This fix is broken. The real problem is win32k, you
should fix that instead.
win32k has no "problem" under this point of view, and as much as we all
like to blame win32k, there is nothing inherently wrong in its use of
ExEnterCriticalRegionAndAcquireFastMutexUnsafe. If you want to explain,
please do