From: Kay Sievers <kay.sievers@vrfy.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Hannes Reinecke <hare@suse.de>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Subtle but oops causing problem with class_device->device conversion
Date: Tue, 29 Jul 2008 19:59:48 +0200 [thread overview]
Message-ID: <1217354388.31362.2.camel@linux.site> (raw)
In-Reply-To: <1217353348.6103.20.camel@localhost.localdomain>
On Tue, 2008-07-29 at 12:42 -0500, James Bottomley wrote:
> It's taken me a while to track this down. Basically there's an oops in
> scsi_transport_spi that's directly caused by this.
>
> What happened is that you made all class devices become real devices and
> be parented to devices they were formerly allied to through the class
> device dev pointer. This means that effectively you expanded the child
> list of every device to include not only its real children but also its
> class devices.
>
> This breaks in device_for_each_child *if* the routine in the iterator
> doesn't perform checks on the devices it gets back (scsi_transport_spi
> was assuming that every device it got was embedded in a struct
> scsi_device because they're the only logical children of a scsi_target).
>
> I can fix the SCSI breakage, but the whole tree will need auditing to
> check that nothing else is using this assumption.
I guess it's caused by:
[SCSI] add scsi_host and scsi_target to scsi_bus
This patch implements scsi_host and scsi_target device types
and adds both to the scsi_bus.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b0ed43360fdca227048d88a08290365cb681c1a8
and not by the re-parenting, so it should be limited to SCSI, right?
Thanks,
Kay
next prev parent reply other threads:[~2008-07-29 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 17:42 Subtle but oops causing problem with class_device->device conversion James Bottomley
2008-07-29 17:59 ` Kay Sievers [this message]
2008-07-29 18:06 ` James Bottomley
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=1217354388.31362.2.camel@linux.site \
--to=kay.sievers@vrfy.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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.