From: Martin Wilck <martin.wilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Cc: dm-devel@lists.linux.dev, Peter Rajnoha <prajnoha@redhat.com>,
Martin Wilck <mwilck@suse.com>
Subject: [PATCH v2 01/11] 11-dm-mpath.rules: explain logic for device becoming ready while suspended
Date: Thu, 4 Apr 2024 19:38:04 +0200 [thread overview]
Message-ID: <20240404173814.3143-2-mwilck@suse.com> (raw)
In-Reply-To: <20240404173814.3143-1-mwilck@suse.com>
Add a comment to explain why we must set MPATH_DEVICE_READY=0 when
we see a device becoming ready (number of active paths 0 -> 1) while
the device is suspended.
Signed-off-by: Martin Wilck <mwilck@suse.com>
---
multipath/11-dm-mpath.rules.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/multipath/11-dm-mpath.rules.in b/multipath/11-dm-mpath.rules.in
index d9585ab..b8d19d0 100644
--- a/multipath/11-dm-mpath.rules.in
+++ b/multipath/11-dm-mpath.rules.in
@@ -98,6 +98,8 @@ ENV{MPATH_DEVICE_READY}=="0", \
# If the device comes back online, set DM_ACTIVATION so that
# upper layers do a rescan. If the device is currently suspended,
# we have to postpone the activation until the next event.
+# In this case, we have to set MPATH_DEVICE_READY=0; otherwise, the
+# MPATH_UNCHANGED logic will cause later rules to skipped in the next event.
ENV{MPATH_DEVICE_READY}=="0", GOTO="dont_activate"
ENV{.MPATH_DEVICE_READY_OLD}!="0", GOTO="dont_activate"
ENV{DM_SUSPENDED}=="1", ENV{MPATH_DEVICE_READY}="0", GOTO="dont_activate"
--
2.44.0
next prev parent reply other threads:[~2024-04-04 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 17:38 [PATCH v2 00/11] multipath udev rules changes for dm rules V3 Martin Wilck
2024-04-04 17:38 ` Martin Wilck [this message]
2024-04-08 18:01 ` [PATCH v2 01/11] 11-dm-mpath.rules: explain logic for device becoming ready while suspended Benjamin Marzinski
2024-04-04 17:38 ` [PATCH v2 02/11] 11-dm-mpath.rules: don't import DM_NOSCAN from udev db Martin Wilck
2024-04-08 18:01 ` Benjamin Marzinski
2024-04-04 17:38 ` [PATCH v2 03/11] 11-dm-mpath.rules: don't import ID_FS_VERSION " Martin Wilck
2024-04-04 17:38 ` [PATCH v2 04/11] 11-dm-mpath.rules: adapt MPATH_DEVICE_READY=0 logic to 10-dm.rules update Martin Wilck
2024-04-08 18:13 ` Benjamin Marzinski
2024-04-04 17:38 ` [PATCH v2 05/11] 11-dm-mpath.rules: adapt coldplug event handling ro " Martin Wilck
2024-04-08 18:33 ` Benjamin Marzinski
2024-04-04 17:38 ` [PATCH v2 06/11] 11-dm-mpath.rules: don't import properties with new 13-dm-disk.rules Martin Wilck
2024-04-08 18:34 ` Benjamin Marzinski
2024-04-04 17:38 ` [PATCH v2 07/11] 11-dm-mpath.rules: replace DM_SUSPENDED by .DM_SUSPENDED Martin Wilck
2024-04-08 18:40 ` Benjamin Marzinski
2024-04-04 17:38 ` [PATCH v2 08/11] 11-dm-mpath.rules: replace DM_NOSCAN by .DM_NOSCAN Martin Wilck
2024-04-08 18:47 ` Benjamin Marzinski
2024-04-09 13:55 ` Martin Wilck
2024-04-04 17:38 ` [PATCH v2 09/11] 11-dm-mpath.rules: simplify PATH_FAILED case Martin Wilck
2024-04-04 17:38 ` [PATCH v2 10/11] 11-dm-mpath.rules: make label names more intuitive Martin Wilck
2024-04-04 17:38 ` [PATCH v2 11/11] kpartx.rules: ignore DM_SUSPENDED Martin Wilck
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=20240404173814.3143-2-mwilck@suse.com \
--to=martin.wilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.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 read-only IMAP folder(s) and NNTP newsgroup(s).