Steven Edwards wrote:
Hi, Royce suggested that we need to get rid of TAG_NONE and I remeber EA posting a list of tags a while back so maybe its a good time to look at the issue again.
http://reactos.com:8080/pipermail/ros-dev/2004-October/000378.html
The complete and most updated list of pool tags is in the file "pooltag.txt", which is distributed with the PoolMon tool.
We have quite a few cases where ExAllocatePool() and ExAllocatePoolWithQuota() is calling ExAllocatePagedPoolWithTag ( TAG_NONE ). I propose that we change the headers for these two functions to throw a compile error if we try to use them internally. We would still keep it implemented to support third party drivers but this way it will force developers to not use them.
I agree. Using untagged memory in kernel mode should be as fatal as calling an unimplemented api.
Emanuele