a496a238e8
The s390 PCI driver assigns the hotplug slot name from the function_id attribute of the PCI device using a 8 char hexadecimal format to match the underlying firmware/hypervisor notation. Further, there's always a one-to-one mapping between a PCI function and a hotplug slot, as individual functions can hot plugged even for multi-function devices. As the generic matching code will always try to parse the slot name in /sys/bus/pci/slots as a positive decimal number, either a wrong value might be produced for ID_NET_NAME_SLOT if the slot name consists of decimal numbers only, or none at all if a character in the range from 'a' to 'f' is encountered. Additionally, the generic code assumes that two interfaces share a hotplug slot, if they differ only in the function part of the PCI address. E.g., for an interface with the PCI address dddd:bb:aa.f, it will match the device to the first slot with an address dddd:bb:aa. As more than one slot may have this address for the s390 PCI driver, the wrong slot may be selected. To resolve this we're adding a new naming schema version with the flag NAMING_SLOT_FUNCTION_ID, which enables the correct matching of hotplug slots if the device has an attribute named function_id. The ID_NET_NAME_SLOT property will only be produced if there's a file /sys/bus/pci/slots/<slotname> where <slotname> matches the value of /sys/bus/pci/devices/.../function_id in 8 char hex notation. Fixes #19016 See also #19078
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.