All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs3 problem with -rc{2,3} : blame
Date: Wed, 20 Jun 2012 00:31:46 +0100	[thread overview]
Message-ID: <20120619233146.GA19796@milliways> (raw)
In-Reply-To: <1340145877.3754.39.camel@lade.trondhjem.org>

On Tue, Jun 19, 2012 at 10:44:38PM +0000, Myklebust, Trond wrote:
> On Tue, 2012-06-19 at 20:35 +0100, Ken Moffat wrote:
> >  Unfortunately, no difference (on top of -rc3).
> > 
> >  FWIW, after rsync stalled I tried a download from firefox, to a
> > different nfs mount, and that too appeared to lock up firefox.
> 
> OK, I think I see what the problem is...
> 
> Does the following patch work for you?
> 
> Cheers
>   Trond
> 8<------------------------------------------------------
> From 1a0de48ae56b5cdb9a46b3d3a0b578dd7f787f22 Mon Sep 17 00:00:00 2001
> From: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date: Tue, 19 Jun 2012 18:38:56 -0400
> Subject: [PATCH] NFS: Initialise commit_info.rpc_out when
>  !defined(CONFIG_NFS_V4)
> 
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> Cc: Fred Isaman <iisaman@netapp.com>
> ---
>  fs/nfs/inode.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
 Yes :)

 On top of 3.5-rc3, without the previous patch.  I did two backups
(different filesystems) and then three downloads from firefox.

 Many thanks!

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce

      reply	other threads:[~2012-06-19 23:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 20:07 nfs3 problem with -rc{2,3} Ken Moffat
2012-06-18  1:11 ` Ken Moffat
2012-06-18 13:42 ` Myklebust, Trond
2012-06-18 13:45   ` Myklebust, Trond
2012-06-18 14:18     ` Ken Moffat
2012-06-18 14:53       ` Myklebust, Trond
2012-06-18 16:00         ` Ken Moffat
2012-06-18 20:05           ` Ken Moffat
2012-06-18 20:11             ` Myklebust, Trond
2012-06-18 23:38               ` Ken Moffat
2012-06-18 23:44                 ` Ken Moffat
2012-06-18 21:53             ` Ken Moffat
2012-06-18 22:03               ` Myklebust, Trond
2012-06-18 22:10                 ` Ken Moffat
2012-06-19  1:06                   ` nfs3 problem with -rc{2,3} : blame Ken Moffat
2012-06-19 16:20                     ` Myklebust, Trond
2012-06-19 16:23                       ` Myklebust, Trond
2012-06-19 16:55                         ` Ken Moffat
2012-06-19 17:46                           ` Myklebust, Trond
2012-06-19 19:35                             ` Ken Moffat
2012-06-19 22:44                               ` Myklebust, Trond
2012-06-19 23:31                                 ` Ken Moffat [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=20120619233146.GA19796@milliways \
    --to=zarniwhoop@ntlworld.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.