public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-scsi@vger.kernel.org
Cc: James Bottomley <jejb@steeleye.com>
Subject: scsi "target1:0:0"
Date: Tue, 16 Nov 2004 17:21:36 +0100	[thread overview]
Message-ID: <1100622096.8606.104.camel@localhost.localdomain> (raw)

Hi,
the recent change to the scsi-sysfs interface broke the operation of
HAL:
  http://hal.freedesktop.org
  http://vrfy.org/projects/hal/HAL-fs-uuid-udi.png
  http://vrfy.org/projects/hal/hal-spec.html

We got an additional directory in the /devices directory which
changed:
  /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/1:0:0:0

to:
  /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/target1:0:0/1:0:0:0

The inserted "target1:0:0" is _not_ backed by any "bus" or "class" device
and therefore breaks the logic of HAL to bring the devices together by
its parent. (We also don't get hotplug events for the "target*" device at
creation time)

Is this intentional and we can not expected a straight chain of devices
anymore like it always was? Shouldn't there be a "class" device to have
it consistent again.

It's the usb-storage driver with an usb-stick.

Thanks,
Kay


[kay@pim ~]$ ls -l /sys/bus/scsi/devices/
total 0
lrwxrwxrwx  1 root root 0 Nov 16 05:40 1:0:0:0 -> ../../../devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/target1:0:0/1:0:0:0




[kay@pim ~]$ ls -l /sys/class/scsi*
/sys/class/scsi_device:
total 0
drwxr-xr-x  2 root root 0 Nov 16 05:27 1:0:0:0

/sys/class/scsi_generic:
total 0
drwxr-xr-x  2 root root 0 Nov 16 05:27 sg0

/sys/class/scsi_host:
total 0
drwxr-xr-x  2 root root 0 Nov 16 05:27 host1




[kay@pim ~]$ ls -l /sys/block/sda/
total 0
-r--r--r--  1 root root 4096 Nov 16 05:40 dev
lrwxrwxrwx  1 root root    0 Nov 16 05:40 device -> ../../devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/target1:0:0/1:0:0:0
drwxr-xr-x  3 root root    0 Nov 16 05:40 queue
-r--r--r--  1 root root 4096 Nov 16 05:40 range
-r--r--r--  1 root root 4096 Nov 16 05:40 removable
drwxr-xr-x  2 root root    0 Nov 16 05:40 sda1
-r--r--r--  1 root root 4096 Nov 16 05:40 size
-r--r--r--  1 root root 4096 Nov 16 05:40 stat




             reply	other threads:[~2004-11-16 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 16:21 Kay Sievers [this message]
2004-11-16 16:33 ` scsi "target1:0:0" James Bottomley
2004-11-16 16:55   ` Kay Sievers
2004-11-16 17:10     ` Matthew Wilcox
2004-11-16 17:23       ` David Zeuthen
2004-11-16 17:25         ` James Bottomley
2004-11-16 17:40           ` David Zeuthen
2004-11-16 19:15         ` greg k-h

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=1100622096.8606.104.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=jejb@steeleye.com \
    --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