On Sat, Jun 20, 2009 at 20:26, Matthew Wilcox<matthew@xxxxxx> wrote:
> On Sat, Jun 20, 2009 at 08:19:43PM +0200, Kay Sievers wrote:
>> On Sat, Jun 20, 2009 at 18:58, Matthew Wilcox<matthew@xxxxxx> wrote:
>>
>> > but I don't know what udev is doing. ??The udev source doesn't seem to
>> > read PCI vpd itself:
>> >
>> > udev-0.141$ find -type f |xargs grep -il vpd
>> > ./extras/volume_id/lib/adaptec_raid.c
>> > ./extras/scsi_id/scsi_id.8
>> > ./extras/scsi_id/scsi.h
>> > ./extras/scsi_id/scsi_id.config
>> > ./extras/scsi_id/scsi_serial.c
>> >
>> > so there must be some script that it's invoking which is doing that.
>> > Anyone familiar with udev?
>>
>> scsi_id is usually also called for cciss devices:
>> KERNEL=="cciss*", ..., IMPORT{program}="scsi_id ...
>
> yes, but it's getting SCSI VPD (by asking for mode pages from the SCSI
> device). This problem is with PCI VPD which is totally different.
Ah, I see. There is no tool around udev, I know of, which does this.
Maybe someone is still using the broken-by-design libsysfs, which
opens _every_ file it can find in /sys, even when not asked for
anything specific.
Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
