[0.4.12][NTOSKRNL] Workaround CORE-16387 & CORE-16449
authorJoachim Henze <Joachim.Henze@reactos.org>
Tue, 6 Oct 2020 15:16:28 +0000 (17:16 +0200)
committerJoachim Henze <Joachim.Henze@reactos.org>
Tue, 6 Oct 2020 15:16:28 +0000 (17:16 +0200)
commit020d470bbd2ca4cffe0291b82ffaca116fbb95ad
tree4b3c4f9f0e1ed6a22e145a35bfd2436656edf60a
parentf0a39c31c9e08b48ca1024a259e446a52b15614c
[0.4.12][NTOSKRNL] Workaround CORE-16387 & CORE-16449

Both was introduced by activating feature
MiWriteProtectSystemImage() once.
Imho this feature is not stable yet, therefore I disable
it for releases.

Both problems most likely got visible by 0.4.12-dev-386-g
65dbfc286818e18095b7cc0c85f63cde6b3e629d

Master remains affected for now.

Worked around like I did for 0.4.13, 0.4.14 already.
ntoskrnl/mm/ARM3/sysldr.c