All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Jeffery <david_jeffery@adaptec.com>
Cc: "Guzovsky, Eduard" <Edg@CROSSBEAMSYS.COM>,
	"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: linux 2.4.18-5 nfs/rpc problem
Date: 10 Oct 2003 15:44:50 -0400	[thread overview]
Message-ID: <shsk77c27yl.fsf@charged.uio.no> (raw)
In-Reply-To: <shsoewo2a4l.fsf@charged.uio.no>

>>>>> " " == Trond Myklebust <trond.myklebust@fys.uio.no> writes:

     > There is indeed one case where this is not being done: in
     > page_launder() you only have a lock on the page. This means
     > that you may end up calling nfs_wait_on_request() in order to
     > flush out a page only to discover that it called iput() from
     > beneath you and is now waiting in clear_inode() on your page
     > lock.

Sorry. I meant 'shrink_cache()'. page_launder() probably disappeared
around 2.4.10 8-).

The point was that writepage() should be the only case where the above
is a problem. I believe readpage does not suffer from the same issue
since it can only be called while the file is still open...

Cheers,
  Trond


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-10-10 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 22:42 linux 2.4.18-5 nfs/rpc problem Guzovsky, Eduard
2003-10-10 17:12 ` David Jeffery
2003-10-10 18:58   ` Trond Myklebust
2003-10-10 19:44     ` Trond Myklebust [this message]
2003-10-13 14:17       ` David Jeffery
2003-10-11  0:18 Guzovsky, Eduard
2003-10-11  0:20 Guzovsky, Eduard

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=shsk77c27yl.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=Edg@CROSSBEAMSYS.COM \
    --cc=david_jeffery@adaptec.com \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.