From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: linux-nfs@vger.kernel.org
Subject: NFSv4.1 assumptions w.r.t. restarting RPC calls.
Date: Mon, 07 Dec 2009 13:36:52 -0500 [thread overview]
Message-ID: <1260211012.32136.48.camel@localhost> (raw)
Currently, the NFSv4.1 implementation of CLOSE/OPEN_DOWNGRADE is
seriously broken because it assumes that nfs4_close_prepare() is
non-idempotent.
I'm planning a fix for that, but does anybody see any other RPC calls
that have the same problem?
Cheers
Trond
next reply other threads:[~2009-12-07 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 18:36 Trond Myklebust [this message]
2009-12-07 21:47 ` [PATCH] NFSv41: Fix a potential state leakage when restarting nfs4_close_prepare Trond Myklebust
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=1260211012.32136.48.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=linux-nfs@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.