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 am using FltCreateSectionForDataScan to read file. Now I want to implement SectionNotificationCallback to hold off conflicting io until I am done with the section.
In my worker thread when I finished with the section:
1) close section(ZwClose + ObDereferenceObject)
2) set notification event(located in section context) indicating that I am done with the section
3) call FltCloseSectionForDataScan + FltReleaseContext
If my SectionNotificationCallback gets called I wait for notification event(in section context) and return from SectionNotificationCallback. It is safe to do so if section context additionally referenced before SectionNotificationCallback. If no additional reference taken before SectionNotificationCallback I can wait on invalid memory (section context destroyed already).
Is my solution ok or I can’t assume additional reference in SectionNotificationCallback ?
|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 Mar 2020||OSR Seminar Space|
|Developing Minifilters||15 Jun 2020||LIVE ONLINE|
|Writing WDF Drivers||22 June 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|