Commit dad255b1 authored by Jeff Layton's avatar Jeff Layton Committed by Steve French

cifs: don't reconnect server when we don't get a response

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: default avatarSuresh Jayaraman <sjayaraman@suse.de>
Reviewed-by: default avatarPavel Shilovsky <piastryyy@gmail.com>
Signed-off-by: default avatarJeff Layton <jlayton@redhat.com>
Signed-off-by: default avatarSteve French <sfrench@us.ibm.com>
parent 0ade640e
...@@ -374,10 +374,8 @@ sync_mid_result(struct mid_q_entry *mid, struct TCP_Server_Info *server) ...@@ -374,10 +374,8 @@ sync_mid_result(struct mid_q_entry *mid, struct TCP_Server_Info *server)
if (mid->midState == MID_REQUEST_SUBMITTED) { if (mid->midState == MID_REQUEST_SUBMITTED) {
if (server->tcpStatus == CifsExiting) if (server->tcpStatus == CifsExiting)
rc = -EHOSTDOWN; rc = -EHOSTDOWN;
else { else
server->tcpStatus = CifsNeedReconnect;
mid->midState = MID_RETRY_NEEDED; mid->midState = MID_RETRY_NEEDED;
}
} }
if (rc != -EHOSTDOWN) { if (rc != -EHOSTDOWN) {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment