From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 3/5] NFS: Never use user credentials for lease renewal
Date: Fri, 28 Jun 2013 20:02:30 +0000 [thread overview]
Message-ID: <1372449749.20188.0.camel@leira.trondhjem.org> (raw)
In-Reply-To: <20130625162346.36416.25389.stgit@seurat.1015granger.net>
On Tue, 2013-06-25 at 12:23 -0400, Chuck Lever wrote:
> Don't try to use a non-UID-0 user credential for lease management,
> as that credential can change out from under us. The server will
> block NFSv4 lease recovery with NFS4ERR_CLID_INUSE.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> fs/nfs/nfs4proc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index d7ba561..5ba38b3 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -6919,7 +6919,7 @@ static const struct nfs4_state_recovery_ops nfs40_reboot_recovery_ops = {
> .recover_open = nfs4_open_reclaim,
> .recover_lock = nfs4_lock_reclaim,
> .establish_clid = nfs4_init_clientid,
> - .get_clid_cred = nfs4_get_setclientid_cred,
> + .get_clid_cred = nfs4_get_exchange_id_cred,
> .detect_trunking = nfs40_discover_server_trunking,
> };
>
> @@ -6942,7 +6942,7 @@ static const struct nfs4_state_recovery_ops nfs40_nograce_recovery_ops = {
> .recover_open = nfs4_open_expired,
> .recover_lock = nfs4_lock_expired,
> .establish_clid = nfs4_init_clientid,
> - .get_clid_cred = nfs4_get_setclientid_cred,
> + .get_clid_cred = nfs4_get_exchange_id_cred,
> };
>
> #if defined(CONFIG_NFS_V4_1)
>
Clearly not compile tested...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2013-06-28 20:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 16:23 [PATCH 0/5] For 3.11 Chuck Lever
2013-06-25 16:23 ` [PATCH 1/5] NFS: Set NFS_CS_MIGRATION for NFSv4 mounts Chuck Lever
2013-06-28 20:03 ` Myklebust, Trond
2013-06-25 16:23 ` [PATCH 2/5] NFS: Use root's credential for lease management when keytab is missing Chuck Lever
2013-06-28 20:11 ` Myklebust, Trond
2013-06-28 20:16 ` Chuck Lever
2013-06-25 16:23 ` [PATCH 3/5] NFS: Never use user credentials for lease renewal Chuck Lever
2013-06-28 20:02 ` Myklebust, Trond [this message]
2013-06-28 20:03 ` Chuck Lever
2013-06-28 20:06 ` Myklebust, Trond
2013-06-25 16:23 ` [PATCH 4/5] NFS: Export _nfs_display_fhandle() Chuck Lever
2013-06-25 16:24 ` [PATCH 5/5] NFS: Save FSID's root FH in nfs_server Chuck Lever
2013-06-25 16:37 ` Myklebust, Trond
2013-06-25 20:22 ` Chuck Lever
2013-06-25 21:15 ` Myklebust, Trond
2013-06-25 21:51 ` Chuck Lever
2013-06-25 22:10 ` Myklebust, Trond
2013-06-26 0:15 ` Chuck Lever
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=1372449749.20188.0.camel@leira.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=chuck.lever@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).