public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code
Date: Mon, 5 May 2003 21:11:58 -0700	[thread overview]
Message-ID: <20030505211158.A14613@beaverton.ibm.com> (raw)
In-Reply-To: <3EB7124C.9010701@torque.net>; from dougg@torque.net on Tue, May 06, 2003 at 11:39:24AM +1000

On Tue, May 06, 2003 at 11:39:24AM +1000, Douglas Gilbert wrote:
> Patrick Mansfield wrote:

> > Yes, it looks very close, and has the underlying infrastructure (uses the
> > SCSI_IOCTL_SEND_COMMAND, not sg, so can be used for all upper level linux
> > scsi devices). It looks like we would need functionallity that is in the
> > devlabel script itself (to output just a  single ID), maybe just integrate
> > that into scsi_unique_id. (I did not look closely at devlabel, it has more
> > lines than the scsi_unique_id.c source.)
> 
> Patrick,
> Even if you don't use sg you still have to use
> the appropriate upper level driver and cope with its
> vagaries (e.g. does it need O_NONBLOCK, could it
> lock you out with O_EXCL). Also you need a device
> file node to open: it may not be there (devfs helps
> here) or could have some tricky symlink.

OK, I suppose those can be worked out one way or another.

The hotplug/sysfs should also give us a kdev that we can use for a
(temporary) mknod - one we can use to get an id (at least for upper level
devices, but I don't see why we would want to get an id for anything else
- if we have no upper level device, we have no user access to the
  scsi_device).

> IMO a safe way to work for disks in lk 2.5 would be to
> scan /sys/block, apply some heuristic to filter out
> degenerate devices, make your own device node (i.e. mknod)
> open it and use the SG_IO ioctl on that fd, etc.
> This method needs root privelege.

I thought Greg's udev approach was going to be for all hotplug, no cold
plug.

> Another approach could be to have a device node for
> the scsi mid level (e.g. /dev/scsi) with an ioctl
> that takes a device's toplogical address and some
> parameters (e.g. VPD_83) and yields the response
> of that INQUIRY (or yields an scsi status and a
> sense buffer).

Can something like that be done for a /dev/sg today? It would be very
useful, not only for VPD/id like commands, but also for user level
scanning.

That is open some /dev/sg via an ioctl (or ?) attach it to a nexus. If
there is an existing scsi_device with a matching nexus, it can attach to
it, else create an sdev via scsi_alloc_sdev, attach to it and go.

Then we can send whatever commands we want via current sg interfaces.

-- Patrick Mansfield

  reply	other threads:[~2003-05-06  4:05 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
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 [this message]
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=20030505211158.A14613@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=dougg@torque.net \
    --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