Jiri Pirko
1f7d0a4674
Some drivers (currently mlx5_core) expose sub-functions (SFs) of a PCI Physical Function as auxiliary devices. Each SF carries a host network interface that sits below the aux device in sysfs: /sys/devices/.../<PF BDF>/mlx5_core.sf.<idx>/net/eth<N> Because the network device's immediate parent is the aux device and not a PCI device, names_pci() bails out and these interfaces fall through to the kernel-assigned eth<N> name, which is not stable across reboots, module reloads or topology changes. The naming applies when the SF network device's direct sysfs parent is the aux device that exposes sfnum, i.e. the kernel driver passes the aux device to SET_NETDEV_DEV(). mlx5_core does so. ice's ice_sf_cfg_netdev() currently passes the parent PF's PCI device, so ice SF network devices sit as siblings of the PF rather than below the aux device and fall outside this precondition; pending a kernel change in ice to mirror mlx5's SET_NETDEV_DEV(netdev, &adev->dev), they continue to receive the kernel-assigned name as they do today. The aux device exposes 'sfnum', the user-defined sub-function number (the value passed to "devlink port add ... sfnum N"), which is stable and unique within its parent PF. The aux device's direct sysfs parent is the PF's PCI device. Treat an SF host network device analogously to an SR-IOV VF host network device: walk to the parent PCI function, derive the base name from there, then append a single-character "S<sfnum>" suffix. Lowercase 's' is already taken (slot) and the existing grammar uses one character per token, so 'S' is the best option. E.g. for an SF whose parent PF is at PCI 0000:c1:00.0 and which was added with "sfnum 88": ID_NET_NAME_PATH=enp193s0f0S88 ID_NET_NAME_SLOT=enp193s0f0S88 This is parallel to how SR-IOV VFs get a "v<N>" suffix on top of the parent PF's name. Gate the new behaviour behind NAMING_SUBFUNC and NAMING_V261. Document the new suffix in both the ID_NET_NAME_SLOT and ID_NET_NAME_PATH grammars in systemd.net-naming-scheme(7) and add a v261 history entry. Co-developed-by: Claude Opus 4.7 <noreply@anthropic.com>
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 Code Map for information about this repository's layout and content.
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, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release