The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I have a crash in my WDF driver in a stress test when I try to deref the Device Extension.
After some debugging it appears that this is caused because on thread in the stress test is unloading the driver while the other still tries to open a handle to it. The device extension is already freed up and hence the call to get the device context returns a NULL pointer.
1. Shouldn't the WDF framework disallow this from happening?
2. Is the something that I need to do in my teardown path to prevent WDF from accepting/forwarding these extra creates?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Internals & Software Drivers||25 Jan 2021||LIVE ONLINE|
|Developing Minifilters||8 March 2021||LIVE ONLINE|