From: David Woodhouse <dwmw2@infradead.org>
To: Jan Hudec <bulb@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suggest TASK_KILLABLE state to overcome most D state trouble
Date: Thu, 27 Sep 2001 22:00:50 +0100 [thread overview]
Message-ID: <19318.1001624450@redhat.com> (raw)
In-Reply-To: <20010927202435.A19466@artax.karlin.mff.cuni.cz>
In-Reply-To: <20010927202435.A19466@artax.karlin.mff.cuni.cz>
bulb@ucw.cz said:
> Does a patch adding a TASK_KILLABLE state have a chance to get in (in
> 2.5)? Or can anybody thik of more elegant solution?
Often there's kernel state which needs to be kept consistent, and locks
which need to be released - just bailing out (as if you got an oops) isn't
sufficient.
What's wrong with the plan of just implementing the appropriate cleanup code
in each buggy or lazy piece of code which sleeps in state
TASK_UNINTERRUPTIBLE, and letting each be interruptible instead?
--
dwmw2
next prev parent reply other threads:[~2001-09-27 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 18:24 Suggest TASK_KILLABLE state to overcome most D state trouble Jan Hudec
2001-09-27 21:00 ` David Woodhouse [this message]
2001-10-01 11:32 ` Jan Hudec
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=19318.1001624450@redhat.com \
--to=dwmw2@infradead.org \
--cc=bulb@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
/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