utils.git, branch master

ccw_init: handle portno option from NM configs

2025-04-08T16:15:41+00:00

ccw.udev: tolerate synthetic ADD and CHANGE uevents

2021-11-26T14:18:52+00:00

Process ADD and CHANGE uevents as prior to the blamed commit. These
can be injected from userspace, and the ADD uevent is important for
devices that get enumerated during early boot (ie. prior to rootfs being
mounted). udev later cold-plugs them into the system via synthetic
ADD uevents (see systemd-udev-trigger.service) to trigger the rule
processing.

As we're not getting synthetic BIND uevents for such devices,
matching on the ADD uevents is needed to get networking set up for
eg. initramfs-less systems.

Note that we're still restricting the matching to devices with the
expected DRIVER attribute.

Fixes: 4b1fc32788a3 ("ccw.udev: match BIND uevent for ccw network devices")
Reported-by: Sven Schnelle 
Signed-off-by: Julian Wiedmann 
Tested-by: Sven Schnelle

ccw_init: use DRIVER environment variable

2021-07-08T07:13:34+00:00

As the ccw.udev rule now only matches BIND uevents, $DRIVER is always
set and we don't need to extract it from sysfs.

Signed-off-by: Julian Wiedmann

ccw.udev: don't match CHANGE uevent for ccw network devices

2021-07-08T07:13:34+00:00

There's nothing in the kernel that would raise a CHANGE uevent for ccw
devices, so don't match it until we know what the semantics might be.

Signed-off-by: Julian Wiedmann

ccw.udev: match BIND uevent for ccw network devices

2021-07-08T07:13:34+00:00

Instead of matching the ADD uevent for a hard-coded list of ccw device
types, wait until the device is actually bound to a driver that follows
the ccwgroup model. This way we don't need to maintain a hard-coded list
of device types, and avoid trying to apply a configuration for devices
that the kernel drivers don't even support.

Also when building the ccwgroup device via /sys/bus/ccwgroup/.../group,
the ccwgroup bus code requires that the ccw devices are bound to the
correct ccw_driver. So matching the ADD uevent seems too early.

This eliminates support of some truly ancient device types (P390, CLAW),
and allows for phasing out support of eg. OSN and OSX.

Note that this requires kernel-side support that was added in 4.14
with commit 1455cf8dbfd0 ("driver core: emit uevents when device is
bound to a driver").

Signed-off-by: Julian Wiedmann

zfcpconf: set exit code explicitly (#1977434)

2021-06-30T09:35:13+00:00

device_cio_free: fix service order after switching to real root file system (#1790496, #1790790)

2021-06-17T07:59:43+00:00

device_cio_free: drop obsolete option in service unit definition

2021-06-16T10:27:42+00:00

update ccw_init and device_cio_free for new NetworkManager default

2020-10-07T12:56:08+00:00

update scripts for https://fedoraproject.org/wiki/Changes/NetworkManager_keyfile_instead_of_ifcfg_rh
that will be implemented in Fedora 33.

In addition to ifcfg files we must look at the NM keyfiles too. New systems
will use keyfiles only, but upgraded systems use ifcfg still.

zfcpconf: add support for automatic LUN scanning

2020-08-25T15:08:07+00:00