A shared section is a security boundary issue. Any low level process can loadlibrary the dll and then manipulate the shared value, affecting the actual umdf process when it is loaded afterwards
d
Bent from my phone
From: Marion Bondmailto:xxxxx
Sent: ?12/?3/?2014 3:54 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] Re: [ntdev] One instance of UMDF device
With the caveat that I have never programmed UMDF my understanding is that they are just a UM DLL so a variable in a shared section should work as a global right?
Sent from Surface Pro
From: xxxxx@osr.commailto:xxxxx
Sent: ?Wednesday?, ?December? ?03?, ?2014 ?5?:?05? ?PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Thanks again, Mr. Wieland.
Might I suggest a doc bug to note under WdfDriverCreate that specifying a Context area for a WDFDRIVER Object with UMDF 2 might not act as expected?
In fact, would it not make sense to actually PREVENT folks from specifying a Context area for a WDFDRIVER (logging something to the log and returning an error to WdfDriverCreate), to avoid what is certainly a difficult to understand problem that’s unique to UMDF? That really would be an insidious problem to find.
Peter
OSR
@OSRDrivers
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>