From: Mike Christie <michaelc@cs.wisc.edu>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-scsi@vger.kernel.org, James Smart <james.smart@emulex.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
Chad Dupuis <chad.dupuis@qlogic.com>,
James Bottomley <jbottomley@parallels.com>
Subject: Re: [PATCH][RFC] scsi_transport_fc: Implement I_T nexus reset
Date: Sun, 09 Dec 2012 17:31:01 -0600 [thread overview]
Message-ID: <50C51F35.2080608@cs.wisc.edu> (raw)
In-Reply-To: <50C51C9C.3060003@cs.wisc.edu>
On 12/09/2012 05:19 PM, Mike Christie wrote:
>
>> >
>>> >>
>>> >>
>>>> >>> @@ -3266,8 +3271,8 @@ fc_timeout_fail_rport_io(struct work_struct *work)
>>>> >>> if (rport->port_state != FC_PORTSTATE_BLOCKED)
>>>> >>> return;
>>>> >>>
>>>> >>> - rport->flags |= FC_RPORT_FAST_FAIL_TIMEDOUT;
>>>> >>> fc_terminate_rport_io(rport);
>>>> >>> + rport->flags |= FC_RPORT_FAST_FAIL_TIMEDOUT;
>>>> >>> }
>>>> >>>
>>> >>
>>> >> What was the reason for moving this? For the eh case in this patch was
>>> >> it causing IO to be failed with DID_TRANSPORT_FAILFAST when we wanted it
>>> >> failed with some other error.
>>> >>
>> > I wanted to ensure that fc_terminate_rport_io() was run when checking
>> > FC_RPORT_FAST_FAIL_TIMEOUT.
>> > Without the move there is a race window between clearing the flag and
>> > calling fc_terminate_rport_io(), which one might trigger by just
>> > checking the flag.
>> >
> What code is this? I am not sure what you mean. fc_terminate_rport_io is
> always going to get run. There does not seem to be checks in it for
> FC_RPORT_FAST_FAIL_TIMEOUT.
Ignore this. I misread your mail. I see what you meant.
next prev parent reply other threads:[~2012-12-09 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 14:51 [PATCH][RFC] scsi_transport_fc: Implement I_T nexus reset Hannes Reinecke
2012-12-07 18:58 ` Mike Christie
2012-12-07 19:58 ` Chad Dupuis
2012-12-07 21:05 ` Jeremy Linton
2012-12-07 21:20 ` Mike Christie
2012-12-07 22:33 ` Jeremy Linton
2012-12-10 10:18 ` Hannes Reinecke
2012-12-09 15:40 ` Hannes Reinecke
2012-12-09 23:19 ` Mike Christie
2012-12-09 23:31 ` Mike Christie [this message]
2012-12-10 2:27 ` Michael Christie
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=50C51F35.2080608@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=andrew.vasquez@qlogic.com \
--cc=chad.dupuis@qlogic.com \
--cc=hare@suse.de \
--cc=james.smart@emulex.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.