Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTFSD

More Info on Driver Writing and Debugging


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/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Good way to detect a DLL unload

AlbertAlbert Member - All Emails Posts: 500

The PsSetLoadImageNotify callback only tells us when a DLL is loaded, and since DLLs are memory mapped, the FILEOBJECT which we get as part of the same callback is also closed immediately after, so tracking IRP_MJ_CLEANUP doesn't cut it.

Is there a good way to track image unloads? Is there a backing FILE_OBJECT for the memory mapped sections which can somehow be used to accomplish this task?

Comments

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,450

    No way...

    There's no callback to tell you when a section is close (i.e. CloseHandle on the section).

    Mm keeps a reference to the first file object used to create the section so that the data can be cached long after it's unmapped/closed. If you see an IRP_MJ_CLOSE for the last file object for the stream you definitively know it's no longer mapped. However, this IRP_MJ_CLOSE may not actually ever arrive (e.g. Mm doesn't purge sections on shutdown)

    -scott
    OSR

  • AlbertAlbert Member - All Emails Posts: 500

    @Scott_Noone_(OSR) said:
    No way...

    There's no callback to tell you when a section is close (i.e. CloseHandle on the section).

    Mm keeps a reference to the first file object used to create the section so that the data can be cached long after it's unmapped/closed. If you see an IRP_MJ_CLOSE for the last file object for the stream you definitively know it's no longer mapped. However, this IRP_MJ_CLOSE may not actually ever arrive (e.g. Mm doesn't purge sections on shutdown)

    So, if I am reading this right, the Destroy event for the stream context also is not guaranteed to tell me about a DLL unload. I was hoping that the stream context destroy event was my only hope here.

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,450

    So, if I am reading this right, the Destroy event for the stream context also is not guaranteed to tell me about a DLL unload. I was hoping that the stream context destroy event was my only hope here.

    Correct. The DLL has to be unloaded for the the stream context destroy callback to fire but the callback can be delayed indefinitely.

    -scott
    OSR

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

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!
Developing Minifilters 24 May 2021 Live, Online
Writing WDF Drivers 14 June 2021 Live, Online
Internals & Software Drivers 27 September 2021 Live, Online
Kernel Debugging 15 November 2021 Live, Online