This is a note to let you know that I've just added the patch titled

    NFSv4: Doh! Typo in the fix to nfs41_walk_client_list

to the 3.8-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:
     nfsv4-doh-typo-in-the-fix-to-nfs41_walk_client_list.patch
and it can be found in the queue-3.8 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From eb04e0ac198cec3bab407ad220438dfa65c19c67 Mon Sep 17 00:00:00 2001
From: Trond Myklebust <[email protected]>
Date: Wed, 10 Apr 2013 12:44:18 -0400
Subject: NFSv4: Doh! Typo in the fix to nfs41_walk_client_list

From: Trond Myklebust <[email protected]>

commit eb04e0ac198cec3bab407ad220438dfa65c19c67 upstream.

Make sure that we set the status to 0 on success. Missed in testing
because it never appears when doing multiple mounts to _different_
servers.

Signed-off-by: Trond Myklebust <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/nfs/nfs4client.c |    1 +
 1 file changed, 1 insertion(+)

--- a/fs/nfs/nfs4client.c
+++ b/fs/nfs/nfs4client.c
@@ -482,6 +482,7 @@ int nfs41_walk_client_list(struct nfs_cl
 
                atomic_inc(&pos->cl_count);
                *result = pos;
+               status = 0;
                dprintk("NFS: <-- %s using nfs_client = %p ({%d})\n",
                        __func__, pos, atomic_read(&pos->cl_count));
                break;


Patches currently in stable-queue which might be from 
[email protected] are

queue-3.8/nfsv4-4.1-fix-bugs-in-nfs4_walk_client_list.patch
queue-3.8/nfsv4-doh-typo-in-the-fix-to-nfs41_walk_client_list.patch
queue-3.8/sunrpc-remove-extra-xprt_put.patch
queue-3.8/nfsv4-fix-a-memory-leak-in-nfs4_discover_server_trunking.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

Reply via email to