Follow-on from previous post - I get an MDL from an internal IOCTL and
pass it to WdfDmaTransactionInitialize, and it crashes with 0x10D (4,
…). It seems that the parameter it doesn’t like VirtualAddress being
0, which I think is a perfectly valid VA - it comes from
MmGetMdlVirtualAddress().
Is this a case of an over-zealous check in WdfDmaTransactionInitialize?
Thanks
James
Yes, it is an over zealous check. I am pretty sure this was fixed in v1.9
d
Sent from my phone with no t9, all spilling mistakes are not intentional.
-----Original Message-----
From: James Harper
Sent: Tuesday, September 08, 2009 11:03 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] bug in WdfDmaTransactionInitialize when VA = NULL
Follow-on from previous post - I get an MDL from an internal IOCTL and
pass it to WdfDmaTransactionInitialize, and it crashes with 0x10D (4,
…). It seems that the parameter it doesn’t like VirtualAddress being
0, which I think is a perfectly valid VA - it comes from
MmGetMdlVirtualAddress().
Is this a case of an over-zealous check in WdfDmaTransactionInitialize?
Thanks
James
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
Yes, it is an over zealous check. I am pretty sure this was fixed in
v1.9
Thanks Doron. I should have mentioned that I am using 1.7 but obviously
you figured that out 
I am working around it by calling MmGetSystemAddressForMdlSafe and then
creating a new MDL from that, which gives me a non-zero VA. Is there a
better way?
Thanks again.
James
That sounds reasonable … or just upgrade now that 1.9 is RTM
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of James Harper
Sent: Tuesday, September 08, 2009 11:47 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] bug in WdfDmaTransactionInitialize when VA = NULL
Yes, it is an over zealous check. I am pretty sure this was fixed in
v1.9
Thanks Doron. I should have mentioned that I am using 1.7 but obviously you figured that out 
I am working around it by calling MmGetSystemAddressForMdlSafe and then creating a new MDL from that, which gives me a non-zero VA. Is there a better way?
Thanks again.
James
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer