From: mwilck@suse.com
To: Jes Sorensen <jsorensen@fb.com>, linux-raid@vger.kernel.org
Cc: lvm-devel@redhat.com, Peter Rajnoha <prajnoha@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Heming Zhao <heming.zhao@suse.com>, Coly Li <colyli@suse.com>,
dm-devel@redhat.com, Martin Wilck <mwilck@suse.com>
Subject: [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG
Date: Wed, 16 Feb 2022 21:59:14 +0100 [thread overview]
Message-ID: <20220216205914.7575-1-mwilck@suse.com> (raw)
From: Martin Wilck <mwilck@suse.com>
device-mapper sets the flag DM_UDEV_DISABLE_OTHER_RULES_FLAG to 1 for
devices which are unusable. They may be no set up yet, suspended, or
otherwise unusable (e.g. multipath maps without usable path). This
flag does not necessarily imply SYSTEMD_READY=0 and must therefore
be tested separately.
Signed-off-by: Martin Wilck <mwilck@suse.com>
---
udev-md-raid-assembly.rules | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/udev-md-raid-assembly.rules b/udev-md-raid-assembly.rules
index d668cdd..4568b01 100644
--- a/udev-md-raid-assembly.rules
+++ b/udev-md-raid-assembly.rules
@@ -21,6 +21,11 @@ IMPORT{cmdline}="noiswmd"
IMPORT{cmdline}="nodmraid"
ENV{nodmraid}=="?*", GOTO="md_inc_end"
+
+# device mapper sets DM_UDEV_DISABLE_OTHER_RULES_FLAG for devices which
+# aren't ready to use
+KERNEL=="dm-*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="md_inc_end"
+
ENV{ID_FS_TYPE}=="ddf_raid_member", GOTO="md_inc"
ENV{noiswmd}=="?*", GOTO="md_inc_end"
ENV{ID_FS_TYPE}=="isw_raid_member", ACTION!="change", GOTO="md_inc"
--
2.35.1
next reply other threads:[~2022-02-16 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 20:59 mwilck [this message]
2022-02-16 22:09 ` [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG NeilBrown
2022-02-17 10:58 ` Martin Wilck
2022-02-17 13:09 ` Peter Rajnoha
2022-02-21 23:36 ` NeilBrown
2022-02-22 13:54 ` Martin Wilck
2022-02-22 22:49 ` NeilBrown
2022-02-23 9:47 ` Martin Wilck
2022-02-28 8:48 ` Martin Wilck
2022-03-18 22:42 ` Martin Wilck
2022-02-28 15:28 ` [dm-devel] " Xiao Ni
2022-03-01 7:53 ` Peter Rajnoha
2022-02-17 13:20 ` Peter Rajnoha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220216205914.7575-1-mwilck@suse.com \
--to=mwilck@suse.com \
--cc=colyli@suse.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=heming.zhao@suse.com \
--cc=jsorensen@fb.com \
--cc=linux-raid@vger.kernel.org \
--cc=lvm-devel@redhat.com \
--cc=prajnoha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).