summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Rajnoha <prajnoha@redhat.com>2023-02-02 15:30:30 +0100
committerPeter Rajnoha <prajnoha@redhat.com>2023-02-02 15:41:47 +0100
commit8498874147c886032817c24d11231947a041bc2e (patch)
tree84d94a31ee0246d2afd135ce3248cbe16e54fea5
parente7c8a825061d57efaffad80667873fa8d68d31ab (diff)
downloadlvm2-8498874147c886032817c24d11231947a041bc2e.tar.gz
udev: remove rule for explicit creation of /dev/mapper/control
We used KERNEL=="device-mapper", NAME="/dev/mapper/control" udev rule to create the /dev/mapper/control file. The "NAME" rule should be only used to rename network devices, otherwise udev issues a warning message. The device-mapper driver has proper DEVNAME=/dev/mapper/control propagated in the uevent environment when it is loaded so we don't need further instruction on where to create the node - udev knows already. Also, these days, it is created directly by kernel inside devtmpfs. This makes the NAME="/dev/mapper/control" rule completely obsolete.
-rw-r--r--WHATS_NEW_DM1
-rw-r--r--udev/10-dm.rules.in2
2 files changed, 1 insertions, 2 deletions
diff --git a/WHATS_NEW_DM b/WHATS_NEW_DM
index 052fb9daf..43bf62a29 100644
--- a/WHATS_NEW_DM
+++ b/WHATS_NEW_DM
@@ -1,5 +1,6 @@
Version 1.02.191 -
=====================================
+ Remove NAME="mapper/control" rule from 10-dm.rules to avoid udev warnings.
Version 1.02.189 - 22nd December 2022
=====================================
diff --git a/udev/10-dm.rules.in b/udev/10-dm.rules.in
index b4fa52ab7..4ffd3e265 100644
--- a/udev/10-dm.rules.in
+++ b/udev/10-dm.rules.in
@@ -28,8 +28,6 @@
# Also, keep in mind that recent rules may also require recent
# subsystem-specific binaries.
-KERNEL=="device-mapper", NAME="(DM_DIR)/control"
-
SUBSYSTEM!="block", GOTO="dm_end"
KERNEL!="dm-[0-9]*", GOTO="dm_end"
(DM_EXEC_RULE)