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 v3 00/12] multipath udev rules changes for dm rules V3
Date: Tue, 9 Apr 2024 16:08:12 +0200 [thread overview]
Message-ID: <20240409140813.26774-1-mwilck@suse.com> (raw)
This patch set adapts the multipath rules to the pending changes
for device mapper rules that update DM_UDEV_RULES_VSN to 3, and
applies some additional clean-ups to the rules files.
Changes v2 -> v3:
* 08/11 replaced another UDEV_RULES_VSN test (Benjamin Marzinski)
(not resending the patches that have already been acked by Ben).
Changes v1 -> v2:
All changes suggested by Benjamin Marzinski except the last one.
* multiple patches: check DM_UDEV_RULES_VSN agains "1|2" rather than "3".
* 01/11: this patch was wrong as discussed, dropped code changes and
added some comments instead, lest I make the same mistake again.
* 02/11: fix label name in comment to match an existing label
* 04/11: added missing "\" at end of line
Comments welcome.
Martin Wilck (12):
11-dm-mpath.rules: explain logic for device becoming ready while
suspended
11-dm-mpath.rules: don't import DM_NOSCAN from udev db
11-dm-mpath.rules: don't import ID_FS_VERSION from udev db
11-dm-mpath.rules: adapt MPATH_DEVICE_READY=0 logic to 10-dm.rules
update
11-dm-mpath.rules: adapt coldplug event handling ro 10-dm.rules update
11-dm-mpath.rules: don't import properties with new 13-dm-disk.rules
11-dm-mpath.rules: replace DM_SUSPENDED by .DM_SUSPENDED
11-dm-mpath.rules: replace DM_NOSCAN by .DM_NOSCAN
11-dm-mpath.rules: simplify PATH_FAILED case
11-dm-mpath.rules: make label names more intuitive
kpartx.rules: ignore DM_SUSPENDED
multipath-tools tests: fix CI failures on arm/v7 with glibc 2.37
kpartx/kpartx.rules | 2 +-
multipath/11-dm-mpath.rules.in | 86 ++++++++++++++++++++--------------
tests/directio.c | 22 ++++-----
tests/vpd.c | 35 +++++++-------
tests/wrap64.h | 23 ++++++++-
5 files changed, 103 insertions(+), 65 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-09 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 14:08 Martin Wilck [this message]
2024-04-09 14:08 ` [PATCH v3 08/12] 11-dm-mpath.rules: replace DM_NOSCAN by .DM_NOSCAN Martin Wilck
2024-04-09 16:39 ` Benjamin Marzinski
2024-04-09 14:14 ` [PATCH v3 00/12] multipath udev rules changes for dm rules V3 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=20240409140813.26774-1-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).