public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandros Batsakis <batsakis@netapp.com>
To: linux-nfs@vger.kernel.org
Cc: trond@netapp.com, Alexandros Batsakis <batsakis@netapp.com>
Subject: [PATCH 0/5] nfs: fix umount - renewd race
Date: Fri,  5 Feb 2010 03:32:29 -0800	[thread overview]
Message-ID: <1265369554-2105-1-git-send-email-batsakis@netapp.com> (raw)

This set contains the first 5 patches from my previous attempt (with an updated changelog).
The RPC patches will follow in a seperate patchset, as we need to further evaluate the proposed
timeout changes.

root (5):
  nfs: kill renewd before clearing client minor version
  nfs: prevent backlogging of renewd requests
  nfs41: renewd sequence operations should take/put client reference
  nfs4: renewd renew operations should take/put a client reference
  nfs4: adjust rpc timeout for nfs_client->rpcclient based on the
    lease_time

 fs/nfs/client.c     |   45 ++++++++++++++++++++++-----------------------
 fs/nfs/nfs4proc.c   |   50 ++++++++++++++++++++++++++++++++++++++++++++++++--
 fs/nfs/nfs4renewd.c |   24 +++++++-----------------
 3 files changed, 77 insertions(+), 42 deletions(-)


             reply	other threads:[~2010-02-11 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 11:32 Alexandros Batsakis [this message]
2010-02-05 11:32 ` [PATCH 1/5] nfs: kill renewd before clearing client minor version Alexandros Batsakis
2010-02-05 11:32   ` [PATCH 2/5] nfs: prevent backlogging of renewd requests Alexandros Batsakis
2010-02-05 11:32     ` [PATCH 3/5] nfs41: renewd sequence operations should take/put client reference Alexandros Batsakis
2010-02-05 11:32       ` [PATCH 4/5] nfs4: renewd renew operations should take/put a " Alexandros Batsakis
2010-02-05 11:32         ` [PATCH 5/5] nfs4: adjust rpc timeout for nfs_client->rpcclient based on the lease_time Alexandros Batsakis

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=1265369554-2105-1-git-send-email-batsakis@netapp.com \
    --to=batsakis@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond@netapp.com \
    /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