> Agreed, but how do you handle the case where your driver is blocked in a
lower-level driver and is never going to come back, because the lower level
driver or device is broke, and you didn’t have any control over what it
waited on?
A broken driver always has the power to corrupt the system.
Don’t know anyway to handle a broken driver except to fix the driver.
(Just to throw some petrol on the fire…)
yes
Lot of time, I’m piggybacking on your thread, and you are piggybacking
on my thread ( on the asynch path … ), but there might be a concept
larking on the horizon that could be called “extreemly lightweight VM
for threads” or lightweight sandbox. Here .NET WOULD play a major role
!!!
(Trying to put water on the fire … 
-prokash
-----Original Message-----
From: Robert Newton [mailto:xxxxx@telusplanet.net]
Sent: Tuesday, February 03, 2004 8:47 AM
To: Windows System Software Devs Interest List
Subject: Re[2]: [ntdev] Gracefully killing a blocked thread
Agreed, but how do you handle the case where your driver is blocked in
a lower-level driver and is never going to come back, because the
lower level driver or device is broke, and you didn’t have any control
over what it waited on?
A broken driver always has the power to corrupt the system. Don’t know
anyway to handle a broken driver except to fix the driver.
(Just to throw some petrol on the fire…)
yes
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@maxtor.com To
unsubscribe send a blank email to xxxxx@lists.osr.com