This is a note to let you know that I've just added the patch titled
NFSv4: nfs4_locku_done must release the sequence id
to the 3.6-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-nfs4_locku_done-must-release-the-sequence-id.patch
and it can be found in the queue-3.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 2b1bc308f492589f7d49012ed24561534ea2be8c Mon Sep 17 00:00:00 2001
From: Trond Myklebust <[email protected]>
Date: Mon, 29 Oct 2012 18:53:23 -0400
Subject: NFSv4: nfs4_locku_done must release the sequence id
From: Trond Myklebust <[email protected]>
commit 2b1bc308f492589f7d49012ed24561534ea2be8c upstream.
If the state recovery machinery is triggered by the call to
nfs4_async_handle_error() then we can deadlock.
Signed-off-by: Trond Myklebust <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
fs/nfs/nfs4proc.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -4390,6 +4390,7 @@ static void nfs4_locku_done(struct rpc_t
if (nfs4_async_handle_error(task, calldata->server,
NULL) == -EAGAIN)
rpc_restart_call_prepare(task);
}
+ nfs_release_seqid(calldata->arg.seqid);
}
static void nfs4_locku_prepare(struct rpc_task *task, void *data)
Patches currently in stable-queue which might be from
[email protected] are
queue-3.6/nfsv3-make-v3-mounts-fail-with-etimedouts-instead-eio-on-mountd-timeouts.patch
queue-3.6/nfs-wait-for-session-recovery-to-finish-before-returning.patch
queue-3.6/nfsv4-nfs4_locku_done-must-release-the-sequence-id.patch
queue-3.6/nfsv4.1-we-must-release-the-sequence-id-when-we-fail-to-get-a-session-slot.patch
queue-3.6/nfs-show-original-device-name-verbatim-in-proc-mount-s-info.patch
queue-3.6/nfs-fix-bug-in-legacy-dns-resolver.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
