Xref: utzoo comp.unix.internals:2123 comp.unix.wizards:24204
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!caen!news.cs.indiana.edu!att!cbnews!rock
From: rock@cbnews.att.com (Y. Rock Lee)
Newsgroups: comp.unix.internals,comp.unix.wizards
Subject: Re: Help with 4.3 mod to kill uninteruptable procs.
Message-ID: <1991Feb21.152845.29019@cbnews.att.com>
Date: 21 Feb 91 15:28:45 GMT
References: <1991Feb19.001941.29928@lynx.CS.ORST.EDU>
Organization: AT&T Bell Laboratories
Lines: 16

In article <1991Feb19.001941.29928@lynx.CS.ORST.EDU> gatesl@mist.cs.orst.edu (Lee Gates) writes:
>	Will the above method cause a race condition resulting from
>the fact that the process probably assumes that the next time it runs 
>it will have the resource it was sleeping on?  And if so, I would
>appreciate some other suggestions as to how to solve this problem.

Yes, the process will think it has the resource it was sleeping on.
But, it will be killed and release the resource during its exit
before it has a chance to "think". This part looks OK to me.
My only concern is that the driver of the particular device which
the process is waiting for may react crazily when it is misinformed
(a good driver should guard against this).


Y. Rock Lee, att!cblph!rock
             rock@cblph.ATT.COM


Brought to you by Super Global Mega Corp .com