ccw.udev: tolerate synthetic ADD and CHANGE ueventsHEADmaster

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 <svens@linux.ibm.com>
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Tested-by: Sven Schnelle <svens@linux.ibm.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/ccw.udev b/ccw.udev
index 8ef72db..c5db932 100644
--- a/ccw.udev
+++ b/ccw.udev
@@ -1,4 +1,4 @@
-ACTION!="bind", GOTO="ccw_end"
+ACTION!="add|bind|change", GOTO="ccw_end"
 SUBSYSTEM!="ccw", GOTO="ccw_end"
 DRIVER=="ctcm|lcs|qeth", RUN+="ccw_init"
 LABEL="ccw_end"