From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] adding per scsi-host workqueues for defered processing
Date: Mon, 7 Mar 2005 23:10:22 -0800 [thread overview]
Message-ID: <20050308071022.GF5141@plap.qlogic.org> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12ECD6@xbl3.ma.emulex.com>
On Sat, 05 Mar 2005, James.Smart@Emulex.Com wrote:
> I've attached a revised patch.
>
> One other note:
> > scsi_scan_target(&rport->dev, rport->channel,
> > rport->scsi_target_id, SCAN_WILD_CARD, 0);
>
> The rescan flag should be 1, not 0. If 0, all kinds of bad things can
> happen as of the 2nd scan request.
>
Unless I'm reading the code incorrectly, we should be safe (only by
possessing some internal knowledge of the mid-layer) passing 0 in
these contexts:
* role change to target -- no previous devices (let alone
scsi-targets) should be hanging off the rport.
* during creation, an rport is newly created with fc_rport_create().
* during creation, an rport was found in the fc_host_rport_bindings'
list. Again, any attached scsi-devices would have been torn-down
prior to the rport being originally placed in the list.
* during an unblock call, where the rport's scsi-devices have already
been torn down since the link-down-tmo had already expired.
But, I suppose in general it's best to play it safe.
--
AV
next prev parent reply other threads:[~2005-03-08 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 13:07 [RFC] adding per scsi-host workqueues for defered processing James.Smart
2005-03-08 7:10 ` Andrew Vasquez [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 5:19 James.Smart
2005-03-09 7:38 ` Andrew Vasquez
2005-03-09 14:25 ` Brian King
2005-03-05 17:30 James.Smart
2005-03-08 7:00 ` Andrew Vasquez
2005-03-08 13:11 ` Luben Tuikov
2005-02-22 4:08 James.Smart
2005-02-22 0:09 Andrew Vasquez
2005-02-22 1:05 ` Matthew Wilcox
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=20050308071022.GF5141@plap.qlogic.org \
--to=andrew.vasquez@qlogic.com \
--cc=James.Smart@Emulex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox