Re: is killing zombies possible w/o a reboot?

[Kyle Moffett]

On Nov 04, 2004, at 22:10, Tim Connors wrote:
> Elladan <elladan@xxxxxxxxxx> said on Thu, 4 Nov 2004 18:38:50 -0800:
> > If a process is in D state and receives a SIGKILL, assume it must exit
> > within a few seconds or it's a bug, and dump as much information about
> > it as is practical...?
>
> Of course, it's not necessarily a bug. Someone could have just kicked
> the ethernet, and so your process is stuck waiting for a read/write.

In any case, if a process is sleeping in-kernel, I expect that either 
it's an
interruptible sleep or a guaranteed-short sleep.  If it's neither, it's 
a bug.  If
I kick out an ethernet and it makes "ping" hang in "D", that's bad.  I 
think
that eventually _all_ kernel sleeps on the behalf of user-space 
processes
will become interruptible.

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a17 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r  
!y?(-)
------END GEEK CODE BLOCK------


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/