Skip to content

Commit

Permalink
cifs: don't reconnect server when we don't get a response
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Jeff Layton authored and Steve French committed Jan 20, 2011
1 parent 0ade640 commit dad255b
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions fs/cifs/transport.c
Original file line number Diff line number Diff line change
Expand Up @@ -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) {
Expand Down

0 comments on commit dad255b

Please sign in to comment.