From: Mi Jinlong <mijinlong@cn.fujitsu.com>
To: NFSv3 list <linux-nfs@vger.kernel.org>,
"Trond.Myklebust" <trond.myklebust@fys.uio.no>,
"J. Bruce Fields" <bfields@fieldses.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@redhat.com>
Subject: [PATCH] sunrpc: cancel delayed connect working when conncet success
Date: Wed, 18 Aug 2010 17:49:30 +0800 [thread overview]
Message-ID: <4C6BACAA.2060706@cn.fujitsu.com> (raw)
As network partition or some other reason, when client connect
success, maybe there is some delayed connect working in connect_work list.
Aug 2 12:51:32 TEST-M kernel: RPC: xs_connect delayed xprt ccc4c800 for 96 seconds
Aug 2 12:51:32 TEST-M kernel: RPC: xs_error_report client ccc4c800...
Aug 2 12:51:32 TEST-M kernel: RPC: error 111
... snip ...
Aug 2 12:53:08 TEST-M kernel: RPC: disconnected transport ccc4c800
Aug 2 12:53:08 TEST-M kernel: RPC: worker connecting xprt ccc4c800 via tcp to 192.168.0.21 (port 2049)
Aug 2 12:53:08 TEST-M kernel: RPC: ccc4c800 connect status 115 connected 0 sock state 2
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_connect_status: retrying
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_prepare_transmit
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_transmit(136)
Aug 2 12:53:08 TEST-M kernel: RPC: xs_tcp_send_request(136) = -11
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xmit incomplete (136 left of 136)
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_connect xprt ccc4c800 is not connected
Aug 2 12:53:08 TEST-M kernel: RPC: xs_connect delayed xprt ccc4c800 for 192 seconds
Aug 2 12:53:08 TEST-M kernel: RPC: xs_tcp_state_change client ccc4c800...
Aug 2 12:53:08 TEST-M kernel: RPC: state 1 conn 0 dead 0 zapped 1
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_connect_status: retrying
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_prepare_transmit
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xprt_transmit(136)
Aug 2 12:53:08 TEST-M kernel: RPC: xs_tcp_send_request(136) = 136
Aug 2 12:53:08 TEST-M kernel: RPC: 228 xmit complete
Aug 2 12:53:08 TEST-M kernel: RPC: 229 xprt_prepare_transmit
As the debug message show, "xs_connect delayed xprt ccc4c800 for 192 seconds"
means a connecting work have be delayed at connect_worker list.
"state 1 conn 0 dead 0 zapped 1" shows the connect have successed
but a delayed work still alive at connect_worker list.
Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
---
net/sunrpc/xprtsock.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
index 49a62f0..823f1db 100644
--- a/net/sunrpc/xprtsock.c
+++ b/net/sunrpc/xprtsock.c
@@ -1324,6 +1324,10 @@ static void xs_tcp_state_change(struct sock *sk)
transport->tcp_flags =
TCP_RCV_COPY_FRAGHDR | TCP_RCV_COPY_XID;
+ if (xprt_connecting(xprt) &&
+ cancel_delayed_work(&transport->connect_worker))
+ xprt_clear_connecting(xprt);
+
xprt_wake_pending_tasks(xprt, -EAGAIN);
}
spin_unlock_bh(&xprt->transport_lock);
--
1.7.0
next reply other threads:[~2010-08-18 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 9:49 Mi Jinlong [this message]
2010-08-30 19:18 ` [PATCH] sunrpc: cancel delayed connect working when conncet success Trond Myklebust
2010-08-31 0:47 ` Mi Jinlong
2010-09-09 10:11 ` Mi Jinlong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C6BACAA.2060706@cn.fujitsu.com \
--to=mijinlong@cn.fujitsu.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox