From: James Bottomley <James.Bottomley@steeleye.com>
To: Mike Anderson <andmike@us.ibm.com>, mochel@osdl.org
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi_set_host_offline (resend)
Date: 25 Mar 2003 11:37:49 -0600 [thread overview]
Message-ID: <1048613872.2070.12.camel@mulgrave> (raw)
In-Reply-To: <20030325100704.GC3868@beaverton.ibm.com>
On Tue, 2003-03-25 at 04:07, Mike Anderson wrote:
This isn't right:
> + spin_lock_irqsave(shost->host_lock, flags);
> + for (lh = shost->my_devices.next;
> + (!error) && (lh != &shost->my_devices);) {
> + sdev = list_entry(lh, struct scsi_device, siblings);
> + scsi_device_get(sdev);
> + spin_unlock_irqrestore(shost->host_lock, flags);
You can't use the host_lock to protect the list and then drop it in the
middle of list traversal. Doing this is bound to have repercussions for
hotplug. I know we're a total mess for hotplug now, but I'd rather not
add to it.
This problem can't be unique to SCSI, so I think what we need is
something like a device generic function, like bus_for_each_device,
except that it's device_for_each_child or something. where we get a
properly ref counted and protected list traversal that will work for
hotplugging.
Pat, can you think of anything nicely generic? We have a non-standard
list to traverse and would probably have to hold the list lock prior to
entry?
James
next prev parent reply other threads:[~2003-03-25 17:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 10:07 [PATCH] scsi_set_host_offline (resend) Mike Anderson
2003-03-25 17:37 ` James Bottomley [this message]
2003-03-25 18:45 ` Mike Anderson
2003-03-25 19:02 ` James Bottomley
2003-03-25 21:04 ` Patrick Mochel
2003-03-25 23:29 ` Mike Anderson
2003-03-27 15:42 ` James Bottomley
2003-03-29 0:31 ` Patrick Mansfield
2003-03-29 1:32 ` Matthew Dharm
2003-03-29 6:30 ` Mike Anderson
2003-03-29 14:43 ` James Bottomley
2003-03-29 19:04 ` Mike Anderson
2003-03-29 19:24 ` Oliver Neukum
2003-03-29 20:53 ` Matthew Dharm
2003-03-29 21:54 ` James Bottomley
2003-03-29 22:15 ` Matthew Dharm
2003-03-30 16:23 ` James Bottomley
2003-03-30 17:26 ` Oliver Neukum
2003-04-09 20:30 ` Luben Tuikov
2003-04-09 22:32 ` Oliver Neukum
2003-04-09 22:59 ` Luben Tuikov
2003-04-10 7:51 ` Oliver Neukum
2003-04-17 22:29 ` Luben Tuikov
2003-03-30 18:21 ` Matthew Dharm
2003-04-09 20:53 ` Luben Tuikov
2003-03-29 22:50 ` Oliver Neukum
2003-04-01 2:48 ` Mike Anderson
2003-04-02 7:42 ` Matthew Dharm
2003-04-03 2:05 ` Mike Anderson
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=1048613872.2070.12.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mochel@osdl.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