From: Valdis.Kletnieks@vt.edu
To: Anthony DiSante <theant@nodivisions.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: uninterruptible sleep lockups
Date: Mon, 21 Feb 2005 14:45:42 -0500 [thread overview]
Message-ID: <200502211945.j1LJjgbZ029643@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 21 Feb 2005 14:18:44 EST." <421A3414.2020508@nodivisions.com>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Mon, 21 Feb 2005 14:18:44 EST, Anthony DiSante said:
> It seems like this problem is always going to exist, because some hardware
> and some drivers will always be buggy. So shouldn't we have some sort of
> watchdog higher up in the kernel, that watches for hung processes like this
> and kills them?
And said watchdog would clean up the mess, how, exactly? There's lots of sticky
issues having to do with breaking locks and possibly still-pending I/O (I once had
a tape drive complete an I/O 3 *days* after the request was sent - good thing no
watchdog killed the process and deallocated the memory that I/O landed in ;)
It's been covered before, look in the lkml archives for details.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2005-02-21 19:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 19:18 Anthony DiSante
2005-02-21 19:45 ` Valdis.Kletnieks [this message]
2005-02-21 20:24 ` Anthony DiSante
2005-02-21 20:54 ` Valdis.Kletnieks
2005-02-21 22:18 ` Anthony DiSante
2005-02-21 22:43 ` Chris Friesen
2005-02-22 0:06 ` Anthony DiSante
2005-02-22 0:36 ` Valdis.Kletnieks
2005-02-21 22:44 ` Anthony DiSante
2005-02-21 23:11 ` Nish Aravamudan
[not found] ` <421B12DB.70603@aitel.hist.no>
2005-02-22 11:16 ` Anthony DiSante
2005-02-22 12:26 ` Denis Vlasenko
2005-02-22 12:35 ` Anthony DiSante
2005-02-22 13:47 ` linux-os
2005-02-22 20:03 ` Anthony DiSante
2005-02-22 20:16 ` Chris Friesen
2005-02-22 20:29 ` Anthony DiSante
2005-02-22 20:24 ` Horst von Brand
2005-02-22 20:56 ` Chris Friesen
2005-02-22 21:40 ` linux-os
2005-02-22 23:17 ` Chris Friesen
2005-02-22 23:42 ` linux-os
2005-02-23 0:25 ` Chris Friesen
2005-02-23 1:05 ` Horst von Brand
2005-02-23 10:04 ` Bernd Petrovitsch
2005-02-22 21:31 ` Olaf Titz
2005-02-23 16:34 ` Nish Aravamudan
[not found] <fa.duv6ag6.p5mth0@ifi.uio.no>
[not found] ` <fa.irk349q.1c3si2o@ifi.uio.no>
2005-02-23 0:59 ` Bodo Eggert
2005-02-23 13:50 ` linux-os
2005-02-24 2:05 ` Bodo Eggert
2005-02-23 16:55 Parag Warudkar
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=200502211945.j1LJjgbZ029643@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=theant@nodivisions.com \
/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
all inboxes | Powered by JetHome®