Re: udev: Inconsistency between %b and %p?

Andreas Schwab wrote:
As I would prefer to use the USB device information (idVendor, idProduct)
to detect the device, I also tried this one:

ATTRS{idVendor}=="0dda", ATTRS{idProduct}=="2005", SUBSYSTEM=="scsi",
ACTION=="add", PROGRAM+="/usr/bin/test.sh %b %p"

Now this version returns the USB device ID ($NUM-$NUM) to the test script,
but the device path (%p) is still OK and still goes down up to the SCSI
device ID.

Why does %b not return the SCSI device ID in the second rule?

Because ATTRS has matched the USB device, not the SCSI device.

Yes, that's right, but "SUBSYSTEM" matched the SCSI device...

If I use udevinfo, then this tool tells me:

| A rule to match, can be composed by the attributes of the device
| and the attributes from one single parent device.

So I thought, that I've matched the SCSI device now. To prove this, I just replaced "SUBSYSTEM=="scsi"" with "SUBSYSTEM=="usb"" and removed the "S" in the "ATTRS" of the above rule, and now, I get the USB-device in %b (as expected) and the path in %p only goes down up to the USB device ID.

So, if all rules match for the same device, then %b and %p are both pointing to this, right, device.

If I try to match, using one of the parent devices (using the "S" "extension" to the property names) and the device, to match to, itself, then the two are inconsistent. Then, %b holds the device name of the parent and %p holds the patch of the device, I want to match.

For me, this looks like a bug, or am I wrong?

Yours

Manuel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: udev: Inconsistency between %b and %p?
    ... but the device path is still OK and still goes down up to the SCSI ... Because ATTRS has matched the USB device, not the SCSI device. ... | and the attributes from one single parent device. ...
    (Linux-Kernel)
  • Re: udev: Inconsistency between %b and %p?
    ... Now this version returns the USB device ID to the test script, ... Because ATTRS has matched the USB device, not the SCSI device. ... SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany ...
    (Linux-Kernel)
  • Re: How to make link between USB physical port and drive letter mount by windows
    ... I don't see how I can get parent device and get "driver key name). ... I can enumerate all USB device with DDK sample but I can't ... manage to find drive letter for each storage. ... The enumerate all DISKs, CDROMs and FLOPPYs. ...
    (microsoft.public.development.device.drivers)
  • Re: How to make link between USB physical port and drive letter mount by windows
    ... I don't see how I can get parent device and get "driver key name). ... I can enumerate all USB device with DDK sample but I can't ... The enumerate all DISKs, CDROMs and FLOPPYs. ...
    (microsoft.public.development.device.drivers)
  • Re: Given a usb mounted storage volume path, how to find usb controlle
    ... Looking at some old code, it appears you used to be able to call SetupDiEnumDeviceInterfaces with the GUID_DEVINTERFACE_VOLUME interface GUID, and then walk up the device tree with CM_Get_Parent and then retrieve the device id with CM_Get_Device_ID. ... However, now, with a storage volume, the parent device is ROOT\VOLMGR\0000, and its parent device is HTREE\ROOT\0. ... So, how do you figure out which USB device is associated with a mounted volume, starting from the volume path? ... but since NT5 it never did for FIXED drives. ...
    (microsoft.public.development.device.drivers)
Loading