From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kay Sievers <kay.sievers@vrfy.org>, Hannes Reinecke <hare@suse.de>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Subtle but oops causing problem with class_device->device conversion
Date: Tue, 29 Jul 2008 12:42:28 -0500 [thread overview]
Message-ID: <1217353348.6103.20.camel@localhost.localdomain> (raw)
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.
James
next reply other threads:[~2008-07-29 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 17:42 James Bottomley [this message]
2008-07-29 17:59 ` Subtle but oops causing problem with class_device->device conversion Kay Sievers
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=1217353348.6103.20.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=hare@suse.de \
--cc=kay.sievers@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox