From: Chris Friesen <cfriesen@nortel.com>
To: linux-os@analogic.com
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
Anthony DiSante <theant@nodivisions.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: uninterruptible sleep lockups
Date: Tue, 22 Feb 2005 17:17:09 -0600 [thread overview]
Message-ID: <421BBD75.6040504@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0502221619330.5460@chaos.analogic.com>
linux-os wrote:
> Now, somebody needs a resource. It executes down(&semaphore);
> once it gets control again, it has that resource. It attempts
> to use that resource through a driver. The driver waits forever.
> The resource is now permanently dorked --forever because its
> driver is waiting forever. The user code never returns from
> the driver so it can never execute up(&semaphore).
What about something like a "robust mutex" (in OSDL terminology)? The
guy holding it too long gets killed, and the mutex gets marked as dirty.
The next guy to aquire the mutex is responsable for re-initializing
the resource (resetting the device to a known state, for instance).
Chris
next prev parent reply other threads:[~2005-02-22 23:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 19:18 uninterruptible sleep lockups Anthony DiSante
2005-02-21 19:45 ` Valdis.Kletnieks
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=421BBD75.6040504@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=theant@nodivisions.com \
--cc=vonbrand@inf.utfsm.cl \
/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