From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] switch scsi upper driver probing to the driver model
Date: Mon, 19 May 2003 14:38:28 -0700 [thread overview]
Message-ID: <20030519143828.A7204@beaverton.ibm.com> (raw)
In-Reply-To: <20030516182039.A7369@lst.de>; from hch@lst.de on Fri, May 16, 2003 at 06:20:39PM +0200
On Fri, May 16, 2003 at 06:20:39PM +0200, Christoph Hellwig wrote:
> Upper drivers now use the LDM ->probe/->remove callbacks and the
> core list code. Note that this means there is only one driver per
> scsi device and not multiple, e.g. you can't have sd _and_ sg for
> the same device. Personally I think that's not a problem anymore
> with the generic SG_IO in place, but if you scream loud enough I
> could come up with a hack that makes the sg nodes a property of the
> scsi midlayer instead of a LDM-style driver and we could get the
> old behaviour back.
The sg attributes (calls to device_create_file) should be removed (at
least until sg has its own class or place to put the attributes), since
sg_probe creates a "type" attribute, then when we return back into
scsi_device_register and try to create the scsi_device "type" attribute,
we fail and call scsi_device_unregister.
And scsi_scan.c ignores the failure, probably leading to some strangeness
or at best a memory leak.
The end result is that there is no scsi_device under sysfs if sg_probe
attached to the scsi_device.
-- Patrick Mansfield
prev parent reply other threads:[~2003-05-19 21:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 16:20 [PATCH] switch scsi upper driver probing to the driver model Christoph Hellwig
2003-05-16 23:57 ` Mike Anderson
2003-05-17 2:25 ` Willem Riede
2003-05-17 7:16 ` Christoph Hellwig
2003-05-17 9:17 ` Christoph Hellwig
2003-05-17 16:35 ` Mike Anderson
2003-05-17 9:59 ` Kai Makisara
2003-05-17 15:08 ` Christoph Hellwig
2003-05-17 16:19 ` James Bottomley
2003-05-18 9:35 ` Kai Makisara
2003-05-17 3:59 ` Douglas Gilbert
2003-05-17 7:13 ` Christoph Hellwig
2003-05-19 19:02 ` Greg KH
2003-05-17 8:32 ` Jens Axboe
2003-05-17 12:52 ` Willem Riede
2003-05-19 21:38 ` Patrick Mansfield [this message]
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=20030519143828.A7204@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@lst.de \
--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