From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: matthias.andree@stud.uni-dortmund.de (Matthias Andree)
Cc: viro@math.psu.edu (Alexander Viro),
matthias.andree@stud.uni-dortmund.de (Matthias Andree),
alex@foogod.com (Alex Stewart),
alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lazy umount (1/4)
Date: Tue, 18 Sep 2001 14:03:50 +0100 (BST) [thread overview]
Message-ID: <E15jKXW-0000sG-00@the-village.bc.nu> (raw)
In-Reply-To: <20010918110815.B16592@emma1.emma.line.org> from "Matthias Andree" at Sep 18, 2001 11:08:15 AM
> something is wrong with the process and it's prone to deadlocks. Even if
> kill -9 just means "fail this all further syscalls instantly" in such
It will already do that. The moment it gets to the syscall return its
history
next prev parent reply other threads:[~2001-09-18 13:00 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 [this message]
2001-09-18 9:07 ` David Woodhouse
2001-09-17 14:43 ` David Woodhouse
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=E15jKXW-0000sG-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alex@foogod.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).