cifs: don't reconnect server when we don't get a response
authorJeff Layton <jlayton@redhat.com>
Tue, 11 Jan 2011 12:24:02 +0000 (07:24 -0500)
committerSteve French <sfrench@us.ibm.com>
Thu, 20 Jan 2011 17:08:50 +0000 (17:08 +0000)
We only want to force a reconnect to the server under very limited and
specific circumstances. Now that we have processes waiting indefinitely
for responses, we shouldn't reach this point unless a reconnect is
already in process. Thus, there's no reason to re-mark the server for
reconnect here.

Reviewed-by: Suresh Jayaraman <sjayaraman@suse.de>
Reviewed-by: Pavel Shilovsky <piastryyy@gmail.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
fs/cifs/transport.c

index c41c9c4f0a79418f630afe46a27525b051c32947..f65cdec042e44c34dea30a21c6b8a3f448f56eb7 100644 (file)
@@ -374,10 +374,8 @@ sync_mid_result(struct mid_q_entry *mid, struct TCP_Server_Info *server)
        if (mid->midState == MID_REQUEST_SUBMITTED) {
                if (server->tcpStatus == CifsExiting)
                        rc = -EHOSTDOWN;
-               else {
-                       server->tcpStatus = CifsNeedReconnect;
+               else
                        mid->midState = MID_RETRY_NEEDED;
-               }
        }
 
        if (rc != -EHOSTDOWN) {