public inbox for linux-kernel@vger.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: Tue, 19 Jun 2012 20:35:40 +0100	[thread overview]
Message-ID: <20120619193540.GA14702@milliways> (raw)
In-Reply-To: <1340127987.3754.16.camel@lade.trondhjem.org>

On Tue, Jun 19, 2012 at 05:46:28PM +0000, Myklebust, Trond wrote:
> 
> Does the following patch make any difference?
> 
> You probably want to ensure that you also have commit
> 906369e43c29001c39c7dfed8a01b9dff24ace75 (which is in 3.5-rc3) since
> that corrects a similar issue.
> 
> Cheers
>   Trond
> 8<------------------------------------------------------------
> From ed3b97f9af6421f326de413e6d6556d1ecc3399d Mon Sep 17 00:00:00 2001
> From: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date: Tue, 19 Jun 2012 13:39:14 -0400
> Subject: [PATCH] NFS: Fix a refcounting issue in O_DIRECT
> 
> In nfs_direct_write_reschedule(), the requests from nfs_scan_commit_list
> have a refcount of 2, whereas the operations in
> nfs_direct_write_completion_ops expect them to have a refcount of 1.
> 
> This patch adds a call to release the extra references.

 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.

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

  reply	other threads:[~2012-06-19 19:35 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 [this message]
2012-06-19 22:44                               ` Myklebust, Trond
2012-06-19 23:31                                 ` Ken Moffat

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=20120619193540.GA14702@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox