This is a note to let you know that I've just added the patch titled
SUNRPC: PipeFS MOUNT notification optimization for dying clients
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:
sunrpc-pipefs-mount-notification-optimization-for-dying-clients.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 <stable@xxxxxxxxxxxxxxx> know about it.
>From 4f6bb246f69443549fbbd0f2abaf863243cb35e9 Mon Sep 17 00:00:00 2001
From: Stanislav Kinsbursky <skinsbursky@xxxxxxxxxxxxx>
Date: Mon, 24 Jun 2013 11:52:59 +0400
Subject: SUNRPC: PipeFS MOUNT notification optimization for dying clients
From: Stanislav Kinsbursky <skinsbursky@xxxxxxxxxxxxx>
commit 4f6bb246f69443549fbbd0f2abaf863243cb35e9 upstream.
Not need to create pipes for dying client. So just skip them.
Note: we can safely dereference the client structure, because notification
caller is holding sn->pipefs_sb_lock.
Signed-off-by: Stanislav Kinsbursky <skinsbursky@xxxxxxxxxxxxx>
Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
net/sunrpc/clnt.c | 2 ++
1 file changed, 2 insertions(+)
--- a/net/sunrpc/clnt.c
+++ b/net/sunrpc/clnt.c
@@ -177,6 +177,8 @@ static inline int rpc_clnt_skip_event(st
if (((event == RPC_PIPEFS_MOUNT) && clnt->cl_dentry) ||
((event == RPC_PIPEFS_UMOUNT) && !clnt->cl_dentry))
return 1;
+ if ((event == RPC_PIPEFS_MOUNT) && atomic_read(&clnt->cl_count) == 0)
+ return 1;
return 0;
}
Patches currently in stable-queue which might be from skinsbursky@xxxxxxxxxxxxx are
queue-3.10/sunrpc-fix-races-on-pipefs-mount-notifications.patch
queue-3.10/sunrpc-fix-races-on-pipefs-umount-notifications.patch
queue-3.10/sunrpc-pipefs-mount-notification-optimization-for-dying-clients.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html