Blame SOURCES/0067-udev-Ignore-change-event-for-imsm.patch

5bf14f
From e1b92ee0de26576a33b20c9dd6ef6bd8cab8e283 Mon Sep 17 00:00:00 2001
5bf14f
From: Mariusz Tkaczyk <mariusz.tkaczyk@intel.com>
5bf14f
Date: Wed, 8 Apr 2020 16:44:52 +0200
5bf14f
Subject: [RHEL7.9 PATCH 67/71] udev: Ignore change event for imsm
5bf14f
5bf14f
When adding a device to a container mdadm has to close its file
5bf14f
descriptor before sysfs_add_disk(). This generates change event.
5bf14f
There is race possibility because metadata is already written and other
5bf14f
-I process can place drive differently. As a result device can be added
5bf14f
to two containers simultaneously.
5bf14f
From IMSM perspective there is no need to react for change event. IMSM
5bf14f
doesn't support stacked devices.
5bf14f
5bf14f
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@intel.com>
5bf14f
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
5bf14f
---
5bf14f
 udev-md-raid-assembly.rules | 2 +-
5bf14f
 1 file changed, 1 insertion(+), 1 deletion(-)
5bf14f
5bf14f
diff --git a/udev-md-raid-assembly.rules b/udev-md-raid-assembly.rules
5bf14f
index 9f055ed..d668cdd 100644
5bf14f
--- a/udev-md-raid-assembly.rules
5bf14f
+++ b/udev-md-raid-assembly.rules
5bf14f
@@ -23,7 +23,7 @@ IMPORT{cmdline}="nodmraid"
5bf14f
 ENV{nodmraid}=="?*", GOTO="md_inc_end"
5bf14f
 ENV{ID_FS_TYPE}=="ddf_raid_member", GOTO="md_inc"
5bf14f
 ENV{noiswmd}=="?*", GOTO="md_inc_end"
5bf14f
-ENV{ID_FS_TYPE}=="isw_raid_member", GOTO="md_inc"
5bf14f
+ENV{ID_FS_TYPE}=="isw_raid_member", ACTION!="change", GOTO="md_inc"
5bf14f
 GOTO="md_inc_end"
5bf14f
 
5bf14f
 LABEL="md_inc"
5bf14f
-- 
5bf14f
2.7.5
5bf14f