This is a note to let you know that I've just added the patch titled
nfsd: set timeparms.to_maxval in setup_callback_client
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
nfsd-set-timeparms.to_maxval-in-setup_callback_client.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 3758cf7e14b753838fe754ede3862af10b35fdac Mon Sep 17 00:00:00 2001
From: Jeff Layton <[email protected]>
Date: Tue, 15 Apr 2014 08:51:48 -0400
Subject: nfsd: set timeparms.to_maxval in setup_callback_client
From: Jeff Layton <[email protected]>
commit 3758cf7e14b753838fe754ede3862af10b35fdac upstream.
...otherwise the logic in the timeout handling doesn't work correctly.
Spotted-by: Trond Myklebust <[email protected]>
Signed-off-by: Jeff Layton <[email protected]>
Signed-off-by: J. Bruce Fields <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
fs/nfsd/nfs4callback.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--- a/fs/nfsd/nfs4callback.c
+++ b/fs/nfsd/nfs4callback.c
@@ -637,9 +637,11 @@ static struct rpc_cred *get_backchannel_
static int setup_callback_client(struct nfs4_client *clp, struct nfs4_cb_conn
*conn, struct nfsd4_session *ses)
{
+ int maxtime = max_cb_time(clp->net);
struct rpc_timeout timeparms = {
- .to_initval = max_cb_time(clp->net),
+ .to_initval = maxtime,
.to_retries = 0,
+ .to_maxval = maxtime,
};
struct rpc_create_args args = {
.net = clp->net,
Patches currently in stable-queue which might be from [email protected] are
queue-3.14/nfsd-set-timeparms.to_maxval-in-setup_callback_client.patch
queue-3.14/nfsd-revert-v2-half-of-nfsd-don-t-return-high-mode-bits.patch
queue-3.14/nfsd-traverse-unconfirmed-client-through-hash-table.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
