From: James Bottomley <James.Bottomley@steeleye.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Douglas Gilbert <dougg@torque.net>,
Andries.Brouwer@cwi.nl,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net,
mdharm-scsi@one-eyed-alien.net
Subject: Re: [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code
Date: 05 May 2003 11:59:10 -0500 [thread overview]
Message-ID: <1052153952.1816.22.camel@mulgrave> (raw)
In-Reply-To: <20030505093834.B7831@beaverton.ibm.com>
On Mon, 2003-05-05 at 11:38, Patrick Mansfield wrote:
> As James said, we can get the uid from user space. This implies we need sg
> (or an equivalent solution).
>
> If the id is required before any actual use of the device, we (sometimes?
> always?) need initramfs.
initramfs is only needed to find the root device. All others can be
located later (although when depends on how the hotplug vs coldplug
issues are sorted out)
> There is a problem with trying to use sg before sg is attached - not sure
> how we can handle this. If sg could be opened generically and attached to
> any nexus (i.e. scsi_device) via ioctl, we could use it not only for id's,
> but for general user level scanning. Or maybe we can wait until after sg
> is attached to get id's.
You can now send SCSI commands directly to sd via the ioctl.
> We still have problems with potentially locking up some devices, and we
> will need some sort of black/white list for VPD usage, this would also
> have been needed for an in kernel implementation; [for user space] you
> would not need a kernel change to fix a problem (modify the black/white
> list or other such code to prevent a VPD from being sent to a particular
> device).
Yes.
> Plus, many of the devices do not return unique id's, even when VPD pages
> are supported (especially I'm told USB) - we need a white list or other
> such mechanism to tell us that id's are actually unique.
That's one of the reasons for moving itt: he heuristics are pretty
complex given the strange things devices seem to call "unique" (I can
even see devices where it's "get the label from the first available
fs").
James
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2003-05-05 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:47 [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code Andries.Brouwer
2003-05-05 7:58 ` Douglas Gilbert
2003-05-05 14:17 ` James Bottomley
2003-05-05 15:52 ` Mike Anderson
2003-05-05 16:14 ` James Bottomley
2003-05-05 16:26 ` Patrick Mansfield
2003-05-05 16:57 ` Mike Anderson
2003-05-05 17:01 ` James Bottomley
2003-05-05 16:38 ` Patrick Mansfield
2003-05-05 16:59 ` James Bottomley [this message]
2003-05-05 17:46 ` Mike Anderson
2003-05-05 22:51 ` Patrick Mansfield
2003-05-06 1:39 ` Douglas Gilbert
2003-05-06 4:11 ` Patrick Mansfield
2003-05-06 5:58 ` Douglas Gilbert
2003-05-06 21:11 ` Patrick Mansfield
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 0:22 Patrick Mansfield
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=1052153952.1816.22.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
/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.