From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: trond.myklebust@fys.uio.no (Trond Myklebust)
Cc: pavel@suse.cz (Pavel Machek), viro@math.psu.edu (Alexander Viro),
alan@lxorguk.ukuu.org.uk (Alan Cox),
Simon.Richter@phobos.fachschaften.tu-muenchen.de (Simon Richter),
jbarker@ebi.ac.uk (Jonathan Barker),
linux-kernel@vger.kernel.org
Subject: Re: VFS mediator?
Date: Tue, 19 Mar 2002 00:15:49 +0000 (GMT) [thread overview]
Message-ID: <E16n7I5-0006SA-00@the-village.bc.nu> (raw)
In-Reply-To: <shs1yeha5b4.fsf@charged.uio.no> from "Trond Myklebust" at Mar 18, 2002 11:18:07 PM
> > Does not work... If you mount nfs server on localhost, you can
> > deadlock.
>
> Huh? Examples please? A hell of a lot of work has gone into ensuring
> that this cannot happen. I do most of my NFS client work on this sort
> of setup, so it had bloody well better work...
At least theoretically it can. Imagine you have every other process stuck
trying to page out (or blocked on a page out) over NFS, including your
user mode nfs process. In practice it would be very hard to arrange but
the theory is real.
Alan
next prev parent reply other threads:[~2002-03-19 0:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:52 VFS mediator? Jonathan Barker
2002-03-14 23:09 ` Simon Richter
2002-03-14 23:33 ` Alan Cox
2002-03-15 0:00 ` Alexander Viro
2002-03-15 11:50 ` Simon Richter
2002-03-18 19:25 ` Pavel Machek
2002-03-18 22:18 ` Trond Myklebust
2002-03-18 22:38 ` Pavel Machek
2002-03-18 22:48 ` Trond Myklebust
2002-03-18 22:54 ` Pavel Machek
2002-03-18 23:05 ` Trond Myklebust
2002-03-19 0:15 ` Alan Cox [this message]
2002-03-18 22:29 ` Alexander Viro
2002-03-18 22:36 ` Pavel Machek
2002-03-15 14:28 ` Jonathan Barker
2002-03-19 13:45 Jesse Pollard
2002-03-19 21:24 ` Pavel Machek
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=E16n7I5-0006SA-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
--cc=jbarker@ebi.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=trond.myklebust@fys.uio.no \
--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).