From: Michael Reed <mdr@sgi.com>
To: linux-scsi@vger.kernel.org, Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Christoph Hellwig <hch@lst.de>, Jeremy Higdon <jeremy@sgi.com>,
James.Smart@Emulex.Com
Subject: qla2x00 driver serialization issue
Date: Mon, 05 Dec 2005 11:35:30 -0600 [thread overview]
Message-ID: <43947A62.8020107@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
With 2.6.15-rc1-git6 (and later), the qla2xxx driver seems to have
a serialization issue which can cause rports to be inappropriately
deleted.
When another hba appears on the fabric, the driver calls
qla2x00_mark_all_devices_lost() which schedules an fc_remote_port_delete()
for all connected rports.
The driver then appears to rediscover targets and re-add them.
Meanwhile, the scheduled work comes in and deletes the targets.
If the scheduled work runs after discovery phase, targets which
should be present are missing from the config.
Attached is an annotated / printk'd dmesg log attempting to
show what is happening. Search for "HERE".
Mike
[-- Attachment #2: dmesg-5.gz --]
[-- Type: application/x-gunzip, Size: 11194 bytes --]
reply other threads:[~2005-12-05 17:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43947A62.8020107@sgi.com \
--to=mdr@sgi.com \
--cc=James.Smart@Emulex.Com \
--cc=andrew.vasquez@qlogic.com \
--cc=hch@lst.de \
--cc=jeremy@sgi.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.