lkml.org 
[lkml]   [2001]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectAbility to kill (was: Re: so, no way to kill process? have to reboot?)
PW> Well, I'd suspect it in "D" state - waiting for some disk I/O to
PW> finish...

If a process is stuck in D state it's a kernel bug - I
don't think it's ever legitimate to wait forever for something
which could never happen. However, some such bugs are rarely
happening (e.g. a swapin failure due to hdd malfunction)
and thus will unlikely be fixed.

PW> But in "R" with your described behavior looks like a bug.
PW> If you care about the CPU time waisted: what about kill -STOP <pid>?

R state unkillable hang is possible too (infinite loop in kernel
preventing return from a syscall).

In short, in my understanding any syscall should return sooner
or later in order to process to be killable. Anything preventing
that is a kernel bug.

However, I'm not a UNIX guru, I may be wrong.
I really like to be enlightened if I'm wrong.
--
Best regards, vda
mailto:vda@port.imtp.ilyichevsk.odessa.ua


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

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.049 / U:1.940 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site