FM / rules.d

/usr/lib/udev/rules.d

Name	Size	Mode	Actions
01-md-raid-creating.rules	321	0644	edit dl rm
39-usbmuxd.rules	991	0644	edit dl rm
40-usb_modeswitch.rules	42861	0644	edit dl rm
40-vm-hotadd.rules	655	0644	edit dl rm
50-apport.rules	165	0644	edit dl rm
50-firmware.rules	210	0644	edit dl rm
50-udev-default.rules	4846	0644	edit dl rm
55-dm.rules	7274	0644	edit dl rm
55-scsi-sg3_id.rules	6664	0644	edit dl rm
56-dm-mpath.rules	4560	0644	edit dl rm
56-dm-parts.rules	1442	0644	edit dl rm
56-lvm.rules	2420	0644	edit dl rm
58-scsi-sg3_symlink.rules	2863	0644	edit dl rm
60-autosuspend.rules	419	0644	edit dl rm
60-block.rules	703	0644	edit dl rm
60-cdrom_id.rules	1071	0644	edit dl rm
60-drm.rules	413	0644	edit dl rm
60-evdev.rules	990	0644	edit dl rm
60-fido-id.rules	491	0644	edit dl rm
60-input-id.rules	282	0644	edit dl rm
60-multipath.rules	3863	0644	edit dl rm
60-open-vm-tools.rules	250	0644	edit dl rm
60-persistent-alsa.rules	616	0644	edit dl rm
60-persistent-input.rules	2719	0644	edit dl rm
60-persistent-storage-dm.rules	1794	0644	edit dl rm
60-persistent-storage-tape.rules	2135	0644	edit dl rm
60-persistent-storage.rules	9145	0644	edit dl rm
60-persistent-v4l.rules	769	0644	edit dl rm
60-sensor.rules	736	0644	edit dl rm
60-serial.rules	1190	0644	edit dl rm
60-tpm-udev.rules	243	0644	edit dl rm
61-persistent-storage-android.rules	455	0644	edit dl rm
63-md-raid-arrays.rules	2452	0644	edit dl rm
64-btrfs-dm.rules	387	0644	edit dl rm
64-btrfs-zoned.rules	346	0644	edit dl rm
64-btrfs.rules	612	0644	edit dl rm
64-md-raid-assembly.rules	1462	0644	edit dl rm
66-azure-ephemeral.rules	1951	0644	edit dl rm
68-del-part-nodes.rules	1141	0644	edit dl rm
69-bcache.rules	1044	0644	edit dl rm
69-lvm-metad.rules	5813	0644	edit dl rm
69-md-clustered-confirm-device.rules	846	0644	edit dl rm
70-iscsi-network-interface.rules	226	0644	edit dl rm
70-joystick.rules	432	0644	edit dl rm
70-memory.rules	184	0644	edit dl rm
70-mouse.rules	734	0644	edit dl rm
70-open-iscsi.rules	253	0644	edit dl rm
70-power-switch.rules	576	0644	edit dl rm
70-touchpad.rules	473	0644	edit dl rm
70-uaccess.rules	2676	0644	edit dl rm
71-power-switch-proliant.rules	461	0644	edit dl rm
71-seat.rules	3810	0644	edit dl rm
73-seat-late.rules	643	0644	edit dl rm
73-special-net-names.rules	969	0644	edit dl rm
75-net-description.rules	480	0644	edit dl rm
75-probe_mtd.rules	174	0644	edit dl rm
77-mm-broadmobi-port-types.rules	936	0644	edit dl rm
77-mm-cinterion-port-types.rules	4401	0644	edit dl rm
77-mm-dell-port-types.rules	1767	0644	edit dl rm
77-mm-dlink-port-types.rules	866	0644	edit dl rm
77-mm-ericsson-mbm.rules	8084	0644	edit dl rm
77-mm-fibocom-port-types.rules	6416	0644	edit dl rm
77-mm-foxconn-port-types.rules	1603	0644	edit dl rm
77-mm-gosuncn-port-types.rules	907	0644	edit dl rm
77-mm-haier-port-types.rules	525	0644	edit dl rm
77-mm-huawei-net-port-types.rules	2596	0644	edit dl rm
77-mm-linktop-port-types.rules	697	0644	edit dl rm
77-mm-longcheer-port-types.rules	14434	0644	edit dl rm
77-mm-mtk-port-types.rules	3282	0644	edit dl rm
77-mm-nokia-port-types.rules	2176	0644	edit dl rm
77-mm-qcom-soc.rules	1619	0644	edit dl rm
77-mm-qdl-device-blacklist.rules	3155	0644	edit dl rm
77-mm-quectel-port-types.rules	7896	0644	edit dl rm
77-mm-sierra.rules	1856	0644	edit dl rm
77-mm-simtech-port-types.rules	3876	0644	edit dl rm
77-mm-telit-port-types.rules	12096	0644	edit dl rm
77-mm-tplink-port-types.rules	739	0644	edit dl rm
77-mm-ublox-port-types.rules	4215	0644	edit dl rm
77-mm-x22x-port-types.rules	4602	0644	edit dl rm
77-mm-zte-port-types.rules	17179	0644	edit dl rm
78-graphics-card.rules	965	0644	edit dl rm
78-sound-card.rules	4816	0644	edit dl rm
80-debian-compat.rules	594	0644	edit dl rm
80-drivers.rules	617	0644	edit dl rm
80-mm-candidate.rules	2142	0644	edit dl rm
80-net-setup-link.rules	295	0644	edit dl rm
80-udisks2.rules	10512	0644	edit dl rm
81-net-dhcp.rules	528	0644	edit dl rm
85-hdparm.rules	82	0644	edit dl rm
90-bolt.rules	359	0644	edit dl rm
90-console-setup.rules	265	0644	edit dl rm
90-fwupd-devices.rules	281	0644	edit dl rm
95-dm-notify.rules	479	0644	edit dl rm
95-kpartx.rules	1401	0644	edit dl rm
95-upower-hid.rules	8109	0644	edit dl rm
95-upower-wup.rules	354	0644	edit dl rm
96-e2scrub.rules	171	0644	edit dl rm
99-lxd-agent.rules	141	0644	edit dl rm
99-systemd.rules	4600	0644	edit dl rm
99-vmware-scsi-udev.rules	433	0644	edit dl rm

Edit: /usr/lib/udev/rules.d/55-dm.rules (7274B)

# Copyright (C) 2009 Red Hat, Inc. All rights reserved.
#
# This file is part of LVM2.

# Udev rules for device-mapper devices.
#
# These rules create a DM control node in /dev/mapper directory.
# The rules also create nodes named dm-x (x is a number) in /dev
# directory and symlinks to these nodes with names given by
# the actual DM names. Some udev environment variables are set
# for use in later rules:
#   DM_NAME - actual DM device's name
#   DM_UUID - UUID set for DM device (blank if not specified)
#   DM_SUSPENDED - suspended state of DM device (0 or 1)
#   DM_UDEV_RULES_VSN - DM udev rules version
#
# These rules cover only basic device-mapper functionality in udev.
#
# Various DM subsystems may contain further subsystem-specific rules
# in 11-dm-<subsystem_name>.rules which should be installed together
# with the DM subsystem and which extend these basic rules.
# For example:
#   11-dm-lvm.rules for LVM subsystem
#   11-dm-mpath.rules for multipath subsystem (since version 0.6.0, recommended!)
#
# Even more specific rules may be required by subsystems so always
# check subsystem's upstream repository for recent set of rules.
# Also, keep in mind that recent rules may also require recent
# subsystem-specific binaries.

KERNEL=="device-mapper", NAME="mapper/control"

SUBSYSTEM!="block", GOTO="dm_end"
KERNEL!="dm-[0-9]*", GOTO="dm_end"

# Device created, major and minor number assigned - "add" event generated.
# Table loaded - no event generated.
# Device resumed (or renamed) - "change" event generated.
# Device removed - "remove" event generated.
#
# The dm-X nodes are always created, even on "add" event, we can't suppress
# that (the node is created even earlier with devtmpfs). All the symlinks
# (e.g. /dev/mapper) are created in right time after a device has its table
# loaded and is properly resumed. For this reason, direct use of dm-X nodes
# is not recommended.
ACTION!="add|change", GOTO="dm_end"

# Decode udev control flags and set environment variables appropriately.
# 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}="/sbin/dmsetup udevflags $env{DM_COOKIE}"

# Rule out easy-to-detect inappropriate events first.
ENV{DISK_RO}=="1", GOTO="dm_disable"

# There is no cookie set nor any flags encoded in events not originating
# in libdevmapper so we need to detect this and try to behave correctly.
# For such spurious events, regenerate all flags from current udev database content
# (this information would normally be inaccessible for spurious ADD and CHANGE events).
ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}=="1", ENV{DM_ACTIVATION}="1", GOTO="dm_flags_done"
IMPORT{db}="DM_UDEV_DISABLE_DM_RULES_FLAG"
IMPORT{db}="DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG"
IMPORT{db}="DM_UDEV_DISABLE_DISK_RULES_FLAG"
IMPORT{db}="DM_UDEV_DISABLE_OTHER_RULES_FLAG"
IMPORT{db}="DM_UDEV_LOW_PRIORITY_FLAG"
IMPORT{db}="DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"
IMPORT{db}="DM_UDEV_PRIMARY_SOURCE_FLAG"
IMPORT{db}="DM_UDEV_FLAG7"
IMPORT{db}="DM_UDEV_RULES"
IMPORT{db}="DM_UDEV_RULES_VSN"
LABEL="dm_flags_done"

# Normally, we operate on "change" events. But when coldplugging, there's an
# "add" event present. We have to recognize this and do our actions in this
# particular situation, too. Also, we don't want the nodes to be created
# prematurely on "add" events while not coldplugging. We check
# DM_UDEV_PRIMARY_SOURCE_FLAG to see if the device was activated correctly
# before and if not, we ignore the "add" event totally. This way we can support
# udev triggers generating "add" events (e.g. "udevadm trigger --action=add" or
# "echo add > /sys/block/<dm_device>/uevent"). The trigger with "add" event is
# also used at boot to reevaluate udev rules for all existing devices activated
# before (e.g. in initrd). If udev is used in initrd, we require the udev init
# script to not remove the existing udev database so we can reuse the information
# stored at the time of device activation in the initrd.
ACTION!="add", GOTO="dm_no_coldplug"
ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}!="1", GOTO="dm_disable"
ENV{DM_ACTIVATION}="1"
LABEL="dm_no_coldplug"

# Putting it together, following table is used to recognize genuine and spurious events.
# N.B. Spurious events are generated based on use of the WATCH udev
# rule or by triggering an event manually by "udevadm trigger" call
# or by "echo <event_name> > /sys/block/dm-X/uevent".
#
#        EVENT              DM_UDEV_PRIMARY_SOURCE_FLAG   DM_ACTIVATION
# ======================================================================
# add event (genuine)                  0                        0
# change event (genuine)               1                        1
# add event (spurious)
#   |_ dev still not active            0                        0
#   \_ dev already active              1                        1
# change event (spurious)
#   |_ dev still not active            0                        0
#   \_ dev already active              1                        0

# "dm" sysfs subdirectory is available in newer versions of DM
# only (kernels >= 2.6.29). We have to check for its existence
# and use dmsetup tool instead to get the DM name, uuid and 
# suspended state if the "dm" subdirectory is not present.
# The "suspended" item was added even later (kernels >= 2.6.31),
# so we also have to call dmsetup if the kernel version used
# is in between these releases.
TEST=="dm", ENV{DM_NAME}="$attr{dm/name}", ENV{DM_UUID}="$attr{dm/uuid}", ENV{DM_SUSPENDED}="$attr{dm/suspended}"
TEST!="dm", IMPORT{program}="/sbin/dmsetup info -j %M -m %m -c --nameprefixes --noheadings --rows -o name,uuid,suspended"
ENV{DM_SUSPENDED}!="?*", IMPORT{program}="/sbin/dmsetup info -j %M -m %m -c --nameprefixes --noheadings --rows -o suspended"

# dmsetup tool provides suspended state information in textual
# form with values "Suspended"/"Active". We translate it to
# 0/1 respectively to be consistent with sysfs values.
ENV{DM_SUSPENDED}=="Active", ENV{DM_SUSPENDED}="0"
ENV{DM_SUSPENDED}=="Suspended", ENV{DM_SUSPENDED}="1"

# This variable provides a reliable way to check that device-mapper
# rules were installed. It means that all needed variables are set
# by these rules directly so there's no need to acquire them again
# later. Other rules can alternate the functionality based on this
# fact (e.g. fallback to rules that behave correctly even without
# these rules installed). It also provides versioning for any
# possible future changes.
# VSN 1 - original rules
# VSN 2 - add support for synthesized events
ENV{DM_UDEV_RULES}="1"
ENV{DM_UDEV_RULES_VSN}="2"

ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*", SYMLINK+="mapper/$env{DM_NAME}"

# Avoid processing and scanning a DM device in the other (foreign)
# rules if it is in suspended state. However, we still keep 'disk'
# and 'DM subsystem' related rules enabled in this case.
ENV{DM_SUSPENDED}=="1", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}="1"

GOTO="dm_end"

LABEL="dm_disable"
ENV{DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG}="1"
ENV{DM_UDEV_DISABLE_DISK_RULES_FLAG}="1"
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}="1"
OPTIONS:="nowatch"

LABEL="dm_end"

cmd: