mirror of
https://github.com/reactos/reactos.git
synced 2024-10-02 07:26:47 +00:00
7b2b759953
[NTOS]: Do a more stringent check to refuse COPY_ON_WRITE flag sent through NtAllocateVirtualMemory. [NTOS]: For VM-based Memory Areas, acquire and then release the process working set lock while inserting the VAD, to simulate what the VAD-based Virtual Memory behavior will look like. [NTOS]: Disable paging for VM-based Memory Areas since this will not be supported with VADs. [KERNEL32]: CopyLoop was requesting 2 zero bits when calling NtAllocateVirtualMemory. Not sure if this was really the intent or not, but both the new as well as the old NtAllocateVirtualMemory do not support this (the new one will ASSERT). Since this functionality never worked, request 0 bits instead to avoid hitting the ASSERT. Any problems with what the VAD system will introduce should be revealed by now. From this build until the one which will have the VAD-based system in place, no further VM-related issues should crop up. svn path=/trunk/; revision=55885 |
||
---|---|---|
reactos | ||
rosapps | ||
rostests | ||
wallpaper |