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

    nfsd4: fix FREE_STATEID lockowner leak

to the 3.10-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:
     nfsd4-fix-free_stateid-lockowner-leak.patch
and it can be found in the queue-3.10 subdirectory.

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


>From 48385408b45523d9a432c66292d47ef43efcbb94 Mon Sep 17 00:00:00 2001
From: "J. Bruce Fields" <[email protected]>
Date: Tue, 27 May 2014 11:14:26 -0400
Subject: nfsd4: fix FREE_STATEID lockowner leak

From: "J. Bruce Fields" <[email protected]>

commit 48385408b45523d9a432c66292d47ef43efcbb94 upstream.

27b11428b7de ("nfsd4: remove lockowner when removing lock stateid")
introduced a memory leak.

Reported-by: Jeff Layton <[email protected]>
Signed-off-by: J. Bruce Fields <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/nfsd/nfs4state.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -3608,7 +3608,7 @@ nfsd4_free_lock_stateid(struct nfs4_ol_s
         * correspondance, and we have to delete the lockowner when we
         * delete the lock stateid:
         */
-       unhash_lockowner(lo);
+       release_lockowner(lo);
        return nfs_ok;
 }
 


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

queue-3.10/nfsd-don-t-try-to-reuse-an-expired-drc-entry-off-the-list.patch
queue-3.10/nfsd4-fix-free_stateid-lockowner-leak.patch
queue-3.10/nfsd-getattr-for-fattr4_word0_files_avail-needs-the-statfs-buffer.patch
queue-3.10/nfsd-don-t-halt-scanning-the-drc-lru-list-when-there-s-an-rc_inprog-entry.patch
queue-3.10/sunrpc-fix-a-module-reference-leak-in-svc_handle_xprt.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