Your driver is not going to use the handle to signal anything. Instead it is
going to use the handle to obtain a pointer to the event object itself,
using ObReferenceObjectByHandle. The driver’s reference on the object
obtained will guarantee that the object will not be deleted until the driver
calls ObDereferenceObject, which it should do as soon as it notices that the
application is terminating.
-----Original Message-----
From: Berto [mailto:xxxxx@wcscnet.com]
Sent: Friday, September 01, 2000 2:47 PM
To: NT Developers Interest List
Subject: [ntdev] What happens if a driver tries to KeSetEvent on a
handle that is no longer valid.I am about to create an interface between an application DLL
and a kernel
driver. The Application/DLL will create a synchronization
event and pass the
handle to the kernel driver allowing it to Signal the event.
My concern is
if for some reason the application crashes, and said event
occurs, what
happens if the event handle is no longer valid? Any suggestions on
protection?Regards
WCSC(Willies Computer Software Co)
http://www.wcscnet.com
Tel: (281)360-4232 Fax: (281)360-3231
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)