Xref: utzoo comp.unix.questions:6968 comp.unix.microport:624
Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!agate!zippy.berkeley.edu!ewv
From: ewv@zippy.berkeley.edu (Eric Varsanyi)
Newsgroups: comp.unix.questions,comp.unix.microport
Subject: Re: Trouble killing processes in SysV/AT
Message-ID: <9873@agate.BERKELEY.EDU>
Date: 11 May 88 22:30:36 GMT
References: <3950@killer.UUCP> <3951@killer.UUCP> <468@micropen>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: ewv@zippy.berkeley.edu.UUCP (Eric Varsanyi)
Organization: University of California, Berkeley
Lines: 10

In article <468@micropen> dave@micropen (David F. Carlson) writes:
> [...]  No close should allow a process
>to wait forever on a event that may not come.  Signals (kill -9) are
>delivered when a process in kernel mode re-enters user mode.  However,
>you process is waiting in kernel mode and won't get those signals til
>its done: NEVER! (or until the long sought interrupt allows it's WCHAN
>to go again.

This is only true if the driver has slept with a wakeup priority < PZERO.
If the process sleeps above PZERO a signal will trash the kernel context
and return to the user with a EINTR (Interrupted system call).