archive mirror
 help / color / mirror / Atom feed
From: Demi Marie Obenour <>
To: LVM general discussion and development <>
Cc: "Marek Marczykowski-Górecki" <>
Subject: [linux-lvm] [PATCH 3/3] Disable udev rules if udev flags can't be obtained
Date: Mon, 4 Apr 2022 17:56:03 -0400	[thread overview]
Message-ID: <Yktpc1D42QLEFqgI@itl-email> (raw)
In-Reply-To: <YktogFA9Lidvo6qa@itl-email>

[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

In this cased the safest option is to disable most udev rules.
 udev/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/udev/ b/udev/
index b4fa52a..9fae8df 100644
--- a/udev/
+++ b/udev/
@@ -50,7 +50,7 @@ ACTION!="add|change", GOTO="dm_end"
 # These flags are encoded in DM_COOKIE variable that was introduced in
 # kernel version 2.6.31. Therefore, we can use this feature with
 # kernels >= 2.6.31 only. Cookie is not decoded for remove event.
-ENV{DM_COOKIE}=="?*", IMPORT{program}="(DM_EXEC)/dmsetup udevflags $env{DM_COOKIE}"
+ENV{DM_COOKIE}=="?*", IMPORT{program}!="(DM_EXEC)/dmsetup udevflags $env{DM_COOKIE}", GOTO="dm_disable"
 # Rule out easy-to-detect inappropriate events first.
 ENV{DISK_RO}=="1", GOTO="dm_disable"
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2022-04-04 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 21:51 [linux-lvm] [PATCH 0/3] Make udev rules more robust Demi Marie Obenour
2022-04-04 21:56 ` Demi Marie Obenour [this message]
2022-04-04 21:58 ` [linux-lvm] [PATCH 1/3] dmsetup: return non-zero on stdio I/O error Demi Marie Obenour
2022-04-04 22:02 ` [linux-lvm] [PATCH 2/3] Disable lvm2 udev rules if `dmsetup splitname` fails Demi Marie Obenour

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yktpc1D42QLEFqgI@itl-email \ \ \ \

* 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).