OSRLogo
OSRLogoOSRLogoOSRLogo x Subscribe to The NT Insider
OSRLogo
x

Everything Windows Driver Development

x
x
x
GoToHomePage xLoginx
 
 

    Sun, 16 Dec 2018     118021 members

   Login
   Join


 
 
Contents
  Online Dump Analyzer
OSR Dev Blog
The NT Insider
Downloads
ListServer / Forum
  Express Links
  · The NT Insider Digital Edition - May-June 2016 Now Available!
  · Windows 8.1 Update: VS Express Now Supported
  · HCK Client install on Windows N versions
  · There's a WDFSTRING?
  · When CAN You Call WdfIoQueueP...ously

No Pool Tagging for Special Pool

During some rotuine testing here at OSR, it became apparent to us that the pool tags associated with allocations that came from Special Pool were not being tracked.  So, we did some checking.

It seems that in both Windows XP (at least through SP1a) and Windows Server 2003 when a driver is run under driver verifier using the "special pool" option, the driver's allocations that come from special pool are not tracked by pool tag.

Sources at Microsoft say that not tracking pool tags for special pool allocations was intentional.  Whether this decision will be changed in future Windows releases or service packs is not known at this time.

Related Articles
Must Succeed Pool...DEAD!
Bagging Bugs — Avoidance and Detection Tips to Consider
Who Owns Which Pool Tag
Permanent Pool Overrun Checking Starting With XP SP2
ExAllocatePoolWithQuota Raises Exceptions
Pool and Memory Events
No Deadlock Verification on x64 UP Systems

User Comments
Rate this article and give us feedback. Do you find anything missing? Share your opinion with the community!
Post Your Comment

"Thanks"
Just wanted to say thanks for this article...I recently got tripped up on this very thing and was good to see it wasn't just me. Does anyone know what the drawback is to turning special pool off? Are there now things I'm potentially missing with the verifier?

Regards,

-Mike Wick

Rating:
06-Apr-04, MICHAEL WICK


Post Your Comments.
Print this article.
Email this article.
bottom nav links