On Tue, Feb 06, 2024 at 04:07:15PM -0600, Bjorn Helgaas wrote:
> Krzysztof has done a ton of work to convert these files to static
> attributes, where the device model prevents most of these races:
>
> 506140f9c06b ("PCI/sysfs: Convert "index", "acpi_index", "label" to static attributes")
> d93f8399053d ("PCI/sysfs: Convert "vpd" to static attribute")
> f42c35ea3b13 ("PCI/sysfs: Convert "reset" to static attribute")
> 527139d738d7 ("PCI/sysfs: Convert "rom" to static attribute")
> e1d3f3268b0e ("PCI/sysfs: Convert "config" to static attribute")
>
> and he even posted a series to do the same for the resource files:
>
> https://lore.kernel.org/linux-pci/20210910202623.2293708-1-kw@xxxxxxxxx/
>
> I can't remember why we didn't apply that at the time, and it no
> longer applies cleanly, but I think that's the direction we should go.
When I brought up resource sysfs files in October, Bjorn said:
I think the reason pci_sysfs_init() exists in the first place is
because those resources may be assigned after pci_device_add(), and
(my memory is hazy here) it seems like changing the size of binary
attributes is hard, which might fit with the
pci_remove_resource_files() and pci_create_resource_files() in the
resource##n##_resize_store() macro
https://lore.kernel.org/all/20231019200110.GA1410324@bhelgaas/
I'm wondering in how far Krzysztof's above-mentioned patches
address the issue of late-appearing resources?
In the meantime I've learned of the existence of sysfs_update_group().
It would seem to me that if resources such as the ROM appear late,
we should just call sysfs_update_group() to make them show up in sysfs
(or correct the size of their sysfs files).
But that requires that we identify the places where resources
are unhidden. Do we know where this happens?
Thanks,
Lukas
