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.

The (most) correct way of telling if closing a file handle is required?

Dejan_MaksimovicDejan_Maksimovic Member - All Emails Posts: 450

Sounds like a newbie question, but it is not..
After a call to APIs like ZwOpenFile/FltCreateFile/ZwCreateKey/etc., what is the most correct way to tell if I need to close a handle?
One would think it is

if(NT_SUCCESS(ntRes))
    ZwClose(hHandle);

But... I have often seen cases where this is not the way to tell if the call to the open API succeeded, as sometimes the return value is a success code, but IoStatus.Status is not, and the actual status is there. This is kinda rare, but often enough that it is not uncatchable.

So... is it:
if(NT_SUCCESS(ntRes) && NT_SUCCESS(IoStatus.Status))
or simply
if(hHandle) // kernel handles are all NULL if invalid, for the above API

?

Regards, Dejan.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

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 24 January 2022 Live, Online
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online