MmGetSystemAddressForMdl will bugcheck the system if there aren’t enough
contiguous system VA pages to map the MDL.
…Safe will return NULL.
In Windows 2000, carrying over into Whistler, we’re trying to eliminate
the reasons why the OS will bugcheck. Forget bugs, things like this are
just far too obvious, and we did succeed in completely cleaning use of
it out of everything internally. Expect next to see
NonPagedPoolMustSucceed get depracated …
MmPrepareMdlForReuse will do the unmap trick, but IoFreeMdl does the
right thing for you anyway. You only need to do this explicitly in very
special circumstances that would have to arise from your driver design;
you won’t encounter them in normal practice. Ex: when you have an MDL
you don’t ever want to free, but want use to map and unmap at will.
Whistler FAT will demonstrate such an example.
-----Original Message-----
From: Neil Weicher [mailto:xxxxx@netlib.com]
Sent: Tuesday, January 02, 2001 6:07 PM
To: File Systems Developers
Subject: [ntfsd] MmGetSystemAddressForMdl obsolete in Win2K?
In my filter driver I am using IoAllocateMdl followed by
MmProbeAndLockPages
and MmGetSystemAddressForMdl. However, Win2K Driver Verifier is telling
me I
should be using MmGetSystemAddressForMdlSafe instead of
MmGetSystemAddressForMdl. Does anyone know what this is about? Is
MmGetSystemAddressForMdl obsolete in Win2K.
On a related note, since MmGetSystemAddressForMdl might call
MmMapLockedPages,
do I also need to call MmUnmapLockedPages at some point?
Thanks (and best wishes to all for a happy new year).
Neil
You are currently subscribed to ntfsd as: xxxxx@exchange.microsoft.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com