Blame SOURCES/0004-udev-adapt-rules-to-systemd-v247.patch

c0f891
From cf9a109209aad285372b67306d54118af6fc522b Mon Sep 17 00:00:00 2001
c0f891
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
c0f891
Date: Fri, 14 Jan 2022 16:44:33 +0100
c0f891
Subject: [PATCH 04/12] udev: adapt rules to systemd v247
c0f891
c0f891
New events have been added in kernel 4.14 ("bind" and "unbind").
c0f891
Systemd maintainer suggests to modify "add|change" branches.
c0f891
This patches implements their suggestions. There is no issue yet because
c0f891
new event types are not used in md.
c0f891
c0f891
Please see systemd announcement for details[1].
c0f891
c0f891
[1] https://lists.freedesktop.org/archives/systemd-devel/2020-November/045646.html
c0f891
c0f891
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
c0f891
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
c0f891
---
c0f891
 udev-md-raid-arrays.rules        | 2 +-
c0f891
 udev-md-raid-assembly.rules      | 5 +++--
c0f891
 udev-md-raid-safe-timeouts.rules | 2 +-
c0f891
 3 files changed, 5 insertions(+), 4 deletions(-)
c0f891
c0f891
diff --git a/udev-md-raid-arrays.rules b/udev-md-raid-arrays.rules
c0f891
index 13c9076e..2967ace1 100644
c0f891
--- a/udev-md-raid-arrays.rules
c0f891
+++ b/udev-md-raid-arrays.rules
c0f891
@@ -3,7 +3,7 @@
c0f891
 SUBSYSTEM!="block", GOTO="md_end"
c0f891
 
c0f891
 # handle md arrays
c0f891
-ACTION!="add|change", GOTO="md_end"
c0f891
+ACTION=="remove", GOTO="md_end"
c0f891
 KERNEL!="md*", GOTO="md_end"
c0f891
 
c0f891
 # partitions have no md/{array_state,metadata_version}, but should not
c0f891
diff --git a/udev-md-raid-assembly.rules b/udev-md-raid-assembly.rules
c0f891
index d668cddd..39b4344b 100644
c0f891
--- a/udev-md-raid-assembly.rules
c0f891
+++ b/udev-md-raid-assembly.rules
c0f891
@@ -30,8 +30,9 @@ LABEL="md_inc"
c0f891
 
c0f891
 # remember you can limit what gets auto/incrementally assembled by
c0f891
 # mdadm.conf(5)'s 'AUTO' and selectively whitelist using 'ARRAY'
c0f891
-ACTION=="add|change", IMPORT{program}="BINDIR/mdadm --incremental --export $devnode --offroot $env{DEVLINKS}"
c0f891
-ACTION=="add|change", ENV{MD_STARTED}=="*unsafe*", ENV{MD_FOREIGN}=="no", ENV{SYSTEMD_WANTS}+="mdadm-last-resort@$env{MD_DEVICE}.timer"
c0f891
+ACTION!="remove", IMPORT{program}="BINDIR/mdadm --incremental --export $devnode --offroot $env{DEVLINKS}"
c0f891
+ACTION!="remove", ENV{MD_STARTED}=="*unsafe*", ENV{MD_FOREIGN}=="no", ENV{SYSTEMD_WANTS}+="mdadm-last-resort@$env{MD_DEVICE}.timer"
c0f891
+
c0f891
 ACTION=="remove", ENV{ID_PATH}=="?*", RUN+="BINDIR/mdadm -If $name --path $env{ID_PATH}"
c0f891
 ACTION=="remove", ENV{ID_PATH}!="?*", RUN+="BINDIR/mdadm -If $name"
c0f891
 
c0f891
diff --git a/udev-md-raid-safe-timeouts.rules b/udev-md-raid-safe-timeouts.rules
c0f891
index 12bdcaa8..2e185cee 100644
c0f891
--- a/udev-md-raid-safe-timeouts.rules
c0f891
+++ b/udev-md-raid-safe-timeouts.rules
c0f891
@@ -50,7 +50,7 @@ ENV{DEVTYPE}!="partition", GOTO="md_timeouts_end"
c0f891
 
c0f891
 IMPORT{program}="/sbin/mdadm --examine --export $devnode"
c0f891
 
c0f891
-ACTION=="add|change", \
c0f891
+ACTION!="remove", \
c0f891
   ENV{ID_FS_TYPE}=="linux_raid_member", \
c0f891
   ENV{MD_LEVEL}=="raid[1-9]*", \
c0f891
   TEST=="/sys/block/$parent/device/timeout", \
c0f891
-- 
c0f891
2.31.1
c0f891