From: Robert Love <rml@tech9.net>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: Amol Lad <dal_loma@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: kill task in TASK_UNINTERRUPTIBLE
Date: 08 May 2002 09:43:30 -0700 [thread overview]
Message-ID: <1020876211.2084.125.camel@bigsur> (raw)
In-Reply-To: <200205081519.g48FJEX24062@Port.imtp.ilyichevsk.odessa.ua>
On Wed, 2002-05-08 at 13:23, Denis Vlasenko wrote:
> On 8 May 2002 12:01, Amol Lad wrote:
> > Hi,
> > Is there any way i can kill a task in
> > TASK_UNINTERRUPTIBLE state ?
>
> No. Everytime you see hung task in this state
> you see kernel bug.
>
> Somebody correct me if I am wrong.
Generally correct. Of course, what is "hung" ?
If it is just sitting in uninterruptible sleep, it could legitimately be
waiting for an event. More than likely, however, after some sane period
of time something is broken.
So, yah, it is a kernel bug.
I'll expand on your answer too - _why_ can't we kill it? Same argument
we had over saving the futexes if a process bails. You hold a semaphore
because you are entering a critical section. If you die in the middle,
who knows the state the data is in and you do _not_ want to reenter it.
Robert Love
next prev parent reply other threads:[~2002-05-08 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 14:01 kill task in TASK_UNINTERRUPTIBLE Amol Lad
2002-05-08 20:23 ` Denis Vlasenko
2002-05-08 16:43 ` Robert Love [this message]
2002-05-08 16:51 ` Philippe Troin
2002-05-08 23:27 ` george anzinger
2002-05-08 23:49 ` Roman Zippel
2002-05-10 20:47 ` Jan Hudec
2002-05-09 15:18 ` Denis Vlasenko
2002-05-09 17:39 ` Andrew Theurer
2002-05-08 18:33 ` Alan Cox
2002-05-09 9:47 ` David Woodhouse
2002-05-09 15:21 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2002-05-09 18:00 Kerl, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1020876211.2084.125.camel@bigsur \
--to=rml@tech9.net \
--cc=dal_loma@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox