From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: NFS list <linux-nfs@vger.kernel.org>,
pNFS Mailing List <pnfs@linux-nfs.org>
Subject: [PATCH 0/3] nfs41 fixes for 2.6.31
Date: Tue, 30 Jun 2009 20:03:32 +0300 [thread overview]
Message-ID: <4A4A4564.3000708@panasas.com> (raw)
Trond,
please consider the following patches for 2.6.31-rc
[PATCH 1/3] nfs41: sunrpc: #include <linux/net.h> from sunrpc.h
fixes compiler warning
[PATCH 2/3] nfs4: record nfs4_reclaim_lease error in cl_cons_state
[PATCH 3/3] nfs41: pass state recovery error back to caller
These 2 patches deal with lease recovery error handling.
This is most visible at mount time when, e.g. when the server exports entry
exported a non-existing path, mounting over nfs4.0 got into a loop
broken only with ^C and mounting with minorversion=1 always returned
the wrong error (-EPROTONOSUPPORT)
fs/nfs/client.c | 10 +++-------
fs/nfs/nfs4proc.c | 16 ++++++++++++----
fs/nfs/nfs4state.c | 2 ++
net/sunrpc/sunrpc.h | 2 ++
4 files changed, 19 insertions(+), 11 deletions(-)
Benny
next reply other threads:[~2009-06-30 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 17:03 Benny Halevy [this message]
2009-06-30 17:06 ` [PATCH 3/3] nfs41: pass state recovery error back to caller Benny Halevy
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=4A4A4564.3000708@panasas.com \
--to=bhalevy@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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