mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Horms <horms@debian.org>
Cc: Marc Horowitz <marc@mit.edu>,
	328135@bugs.debian.org, linux-kernel@vger.kernel.org
Subject: Re: Bug#328135: kernel-image-2.6.11-1-686-smp: nfs reading process stuck in disk wait
Date: Thu, 15 Sep 2005 10:44:39 +0100	[thread overview]
Message-ID: <1126777479.12556.55.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20050915092246.GE25382@verge.net.au>

to den 15.09.2005 Klokka 18:22 (+0900) skreiv Horms:
> I take it from your initial remarks that the use of sync_page()
> in the VSF has changed recently. And in any case, it would
> be worth testing 2.6.12 or 2.6.13 before investigating any further
> as in your oppinion the problem is not NFS related, but related
> to somthing that NFS coincidently triggers (but could just as
> easily triggered by anything else).

Right. What I'm saying is that NFS has no special hooks inside
lock_page(), so this is 100% generic VFS code.

Cheers,
  Trond


  reply	other threads:[~2005-09-15  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050913194707.8C8C28E6F0@ayer.connecterra.net>
2005-09-14  2:51 ` Horms
2005-09-14 23:58   ` Trond Myklebust
2005-09-15  1:10     ` Marc Horowitz
2005-09-15  8:32       ` Trond Myklebust
2005-09-15  9:22         ` Horms
2005-09-15  9:44           ` Trond Myklebust [this message]
2005-09-15 14:29         ` Marc Horowitz
     [not found] <4Mpqc-7h0-23@gated-at.bofh.it>
     [not found] ` <4MxnE-1Z7-5@gated-at.bofh.it>
     [not found]   ` <4MPuc-4iZ-1@gated-at.bofh.it>
     [not found]     ` <4MQzZ-5PL-9@gated-at.bofh.it>
     [not found]       ` <4MXrT-7xn-29@gated-at.bofh.it>
     [not found]         ` <4N34g-7De-15@gated-at.bofh.it>
2005-09-15 18:46           ` Nigel Kukard

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=1126777479.12556.55.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=328135@bugs.debian.org \
    --cc=horms@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@mit.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

all inboxes | Powered by JetHome®