public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lazy umount (1/4)
Date: Mon, 17 Sep 2001 15:43:16 +0100	[thread overview]
Message-ID: <22094.1000737796@redhat.com> (raw)
In-Reply-To: <20010917120428.A13815@emma1.emma.line.org>
In-Reply-To: <20010917120428.A13815@emma1.emma.line.org>  <Pine.GSO.4.21.0109141427070.11172-100000@weyl.math.psu.edu>


matthias.andree@stud.uni-dortmund.de said:
>  Well, from a practical point of view two things that would really
> help Linux:

> 1) Be able kill -9 processes from "D" state. 

'D' state means _uninterruptible_ sleep. To be interruptible, we need to
have appropriate cleanup code at the point at which the code sleeps. Often,
parts of the kernel sleep in 'D' state instead of in 'S' state just because
someone's been too lazy to implement the cleanup.

Each one of those bugs needs to be fixed individually - and many need core
changes. Fixing read_inode() so that well-behaved filesystems can deal with
being interrupted during its operation is on the list for 2.5. Others will
be required too, I'm sure.

--
dwmw2



      parent reply	other threads:[~2001-09-17 14:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 19:01 [PATCH] lazy umount (1/4) Alexander Viro
2001-09-14 19:02 ` [PATCH] lazy umount (2/4) Alexander Viro
2001-09-14 19:03   ` [PATCH] lazy umount (3/4) Alexander Viro
2001-09-14 19:03     ` [PATCH] lazy umount (4/4) Alexander Viro
2001-09-14 20:43 ` [PATCH] lazy umount (1/4) Linus Torvalds
2001-09-14 20:54   ` Alexander Viro
2001-09-15 12:32 ` jlnance
2001-09-15 20:51   ` Mike Fedyk
2001-09-17 10:06     ` Matthias Andree
2001-09-16 16:37 ` Alex Stewart
2001-09-17  6:57   ` Forced umount (was lazy umount) Ville Herva
2001-09-17  7:03     ` Aaron Lehmann
2001-09-17  8:38       ` Alexander Viro
2001-09-17 10:21         ` Matthias Andree
2001-09-17 10:47           ` Tigran Aivazian
2001-09-17 23:21             ` Alex Stewart
2001-09-17 23:23               ` Xavier Bestel
2001-09-18  1:04                 ` Alex Stewart
2001-09-18 20:19                   ` Pavel Machek
2001-09-17  8:29     ` Xavier Bestel
2001-09-17  8:39       ` Alexander Viro
2001-09-17 10:04 ` [PATCH] lazy umount (1/4) Matthias Andree
2001-09-17 12:13   ` Alan Cox
2001-09-18  0:24     ` Alex Stewart
2001-09-18  0:39       ` Matthias Andree
2001-09-18  8:56         ` Alexander Viro
2001-09-18  9:08           ` Matthias Andree
2001-09-18 13:03             ` Alan Cox
2001-09-18  9:07     ` David Woodhouse
2001-09-17 14:43 ` David Woodhouse [this message]

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=22094.1000737796@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    /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