Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
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 just noticed a possible documentation error for the function KeTryToAcquireSpinLockAtDpcLevel(), it says that you should release the spin lock with KeReleaseSpinLock() but all the other "AtDpcLevel" functions has a separate release function that is called KeReleaseSpinLockFromDpcLevel() so I would like to ask if this is a documentation error or if there is something special with the "Try" function so it is true you should use the ordinary release function?
|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!|
|Kernel Debugging||30 January 2023||Live, Online|
|Developing Minifilters||20 March 2023||Live, Online|
|Internals & Software Drivers||17 April 2023||Live, Online|
|Writing WDF Drivers||22 May 2023||Live, Online|
Exactly! There are no saved IRQL to give to the release function, however it would work if one gives it the "false" value DPC_LEVEL!
Normally the IRQL is inferred from control flow. If you are confident to call KeAcquireSpinLockAtDpcLevel, you should be confident that you know what to pass to KeReleaseSpinLock.