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/
In my testing it appears that
IoVerifyVolume can leak the VPB of the passed device. This happens in either of these 2 cases:
In either of these cases
IoVerifyVolume attempts to (re-)mount the device. For this purpose it creates a new VPB using
IopCreateVpb, but it does so without regard of whether a VPB exists already.
IopCreateVpb appears to simply overwrite the
In my testing at least this appears to create a memory leak. Indeed if I modify my driver so that it frees that old VPB, the system chugs along without any complains about double frees or anything like that. (And yes, I always run my driver tests with verifier enabled).
This problem appears to exist in at least Win10 2004, but I believe it also exists in earlier and later versions of the OS.
Have I misunderstood
IoVerifyVolume and how to use it?
|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||12 September 2022||Live, Online|
|Internals & Software Drivers||23 October 2022||Live, Online|
|Kernel Debugging||14 November 2022||Live, Online|
|Developing Minifilters||5 December 2022||Live, Online|