Commit 73b43764 authored by Mike Christie's avatar Mike Christie Committed by James Bottomley

[SCSI] libfc: fix setting of rport dev loss

There does not seem to be a reason why libfc adds a 5
second delay to the user requested value for the dev loss
tmo. There also does not seem to be a reason to allow
setting it to 0 (or really close).

This patch removes the extra 5 sec delay, and for 0 it
sets it to 1 like other fc drivers. We should actually
be able to set it to 0 since the queue_delayed_work API
will just call queue_work, but other drivers set it to 1 in
that case.
Signed-off-by: default avatarMike Christie <michaelc@cs.wisc.edu>
Signed-off-by: default avatarRobert Love <robert.w.love@intel.com>
Signed-off-by: default avatarJames Bottomley <James.Bottomley@suse.de>
parent f63ae56e
...@@ -196,9 +196,9 @@ static const char *fc_rport_state(struct fc_rport_priv *rdata) ...@@ -196,9 +196,9 @@ static const char *fc_rport_state(struct fc_rport_priv *rdata)
void fc_set_rport_loss_tmo(struct fc_rport *rport, u32 timeout) void fc_set_rport_loss_tmo(struct fc_rport *rport, u32 timeout)
{ {
if (timeout) if (timeout)
rport->dev_loss_tmo = timeout + 5; rport->dev_loss_tmo = timeout;
else else
rport->dev_loss_tmo = 30; rport->dev_loss_tmo = 1;
} }
EXPORT_SYMBOL(fc_set_rport_loss_tmo); EXPORT_SYMBOL(fc_set_rport_loss_tmo);
......
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