From 252239bdac59a4fcfd7b9279a1df2c965e9cf0fa Mon Sep 17 00:00:00 2001 From: Alasdair Kergon Date: Mon, 3 Aug 2009 18:44:54 +0000 Subject: [PATCH] Add default udev rules. Update dm-ioctl.h comments. --- libdm/misc/dm-ioctl.h | 14 ++++++++++-- udev/10-dm.rules.in | 44 ++++++++++++++++++++++++++++++++++++ udev/11-dm-permissions.rules | 18 +++++++++++++++ udev/11-lvm.rules | 32 ++++++++++++++++++++++++++ udev/12-dm-disk.rules | 30 ++++++++++++++++++++++++ udev/95-dm-notify.rules | 16 +++++++++++++ udev/Makefile.in | 29 ++++++++++++++++++++++++ 7 files changed, 181 insertions(+), 2 deletions(-) create mode 100644 udev/10-dm.rules.in create mode 100644 udev/11-dm-permissions.rules create mode 100644 udev/11-lvm.rules create mode 100644 udev/12-dm-disk.rules create mode 100644 udev/95-dm-notify.rules diff --git a/libdm/misc/dm-ioctl.h b/libdm/misc/dm-ioctl.h index b6028f301..8222a75d1 100644 --- a/libdm/misc/dm-ioctl.h +++ b/libdm/misc/dm-ioctl.h @@ -125,6 +125,16 @@ struct dm_ioctl { uint32_t target_count; /* in/out */ int32_t open_count; /* out */ uint32_t flags; /* in/out */ + + /* + * event_nr holds either the event number (input and output) or the + * udev cookie value (input only). + * The DM_DEV_WAIT ioctl takes an event number as input. + * The DM_SUSPEND, DM_DEV_REMOVE and DM_DEV_RENAME ioctls + * use the field as a cookie to return in the DM_COOKIE + * variable with the uevents they issue. + * For output, the ioctls return the event number, not the cookie. + */ uint32_t event_nr; /* in/out */ uint32_t padding; @@ -258,9 +268,9 @@ enum { #define DM_DEV_SET_GEOMETRY _IOWR(DM_IOCTL, DM_DEV_SET_GEOMETRY_CMD, struct dm_ioctl) #define DM_VERSION_MAJOR 4 -#define DM_VERSION_MINOR 14 +#define DM_VERSION_MINOR 15 #define DM_VERSION_PATCHLEVEL 0 -#define DM_VERSION_EXTRA "-ioctl (2008-04-23)" +#define DM_VERSION_EXTRA "-ioctl (2009-04-01)" /* Status bits */ #define DM_READONLY_FLAG (1 << 0) /* In/Out */ diff --git a/udev/10-dm.rules.in b/udev/10-dm.rules.in new file mode 100644 index 000000000..e0de5d3ee --- /dev/null +++ b/udev/10-dm.rules.in @@ -0,0 +1,44 @@ +# Udev rules for device-mapper devices. +# +# These rules create a DM control node in /dev/(DM_DIR) 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) + +KERNEL=="device-mapper", NAME="(DM_DIR)/control" + +SUBSYSTEM!="block", GOTO="dm_end" +KERNEL!="dm-[0-9]*", GOTO="dm_end" +ACTION!="add|change", GOTO="dm_end" + +# Normally, we operate on "change" events only. 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. +ACTION=="add", ENV{STARTUP}!="1", NAME="", GOTO="dm_end" + +# "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 >= ???), +# 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" + +ENV{DM_NAME}=="?*", NAME="$kernel", SYMLINK+="(DM_DIR)/$env{DM_NAME}" + +LABEL="dm_end" diff --git a/udev/11-dm-permissions.rules b/udev/11-dm-permissions.rules new file mode 100644 index 000000000..1e9cdfdbc --- /dev/null +++ b/udev/11-dm-permissions.rules @@ -0,0 +1,18 @@ +# Udev rules for device-mapper devices. +# +# These rules set permissions for DM devices. There are some environment +# variables set that can be used: +# 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_LV_NAME - logical volume name (not set if LVM device not present) +# DM_VG_NAME - volume group name (not set if LVM device not present) +# DM_LV_LAYER - logical volume layer (not set if LVM device not present) + +SUBSYSTEM!="block", GOTO="dm_end" +KERNEL!="dm-[0-9]*", GOTO="dm_end" +ACTION!="change", GOTO="dm_end" + +#ENV{DM_NAME}=="my_device", OWNER:="peter", GROUP:="peter", MODE:="644" + +LABEL="dm_end" diff --git a/udev/11-lvm.rules b/udev/11-lvm.rules new file mode 100644 index 000000000..8dfaa6412 --- /dev/null +++ b/udev/11-lvm.rules @@ -0,0 +1,32 @@ +# Udev rules for LVM. +# +# These rules create symlinks for LVM logical volumes in +# /dev/VG directory (VG is an actual VG name). Some udev +# environment variables are set (they can be used in later +# rules as well): +# DM_LV_NAME - logical volume name +# DM_VG_NAME - volume group name +# DM_LV_LAYER - logical volume layer (blank if not set) + +SUBSYSTEM!="block", GOTO="lvm_end" +KERNEL!="dm-[0-9]*", GOTO="lvm_end" +ACTION!="add|change", GOTO="lvm_end" +ENV{DM_UUID}!="LVM-?*", GOTO="lvm_end" + +# Normally, we operate on "change" events only. But when +# coldplugging, there's an "add" event present. We have +# to recognize this and do our actions in this particular +# situation, too. +ACTION=="add", ENV{STARTUP}!="1", GOTO="lvm_end" + +# Use DM name and split it up into its VG/LV/layer constituents. +IMPORT{program}="/sbin/dmsetup namesplit --nameprefixes --noheadings --rows $env{DM_NAME}" + +# Do not create symlinks for hidden subdevices. +ENV{DM_LV_NAME}=="?*_mlog", GOTO="lvm_end" +ENV{DM_LV_NAME}=="?*_mimage_[0-9]*", GOTO="lvm_end" + +# Create symlinks for top-level devices only. +ENV{DM_VG_NAME}=="?*", ENV{DM_LV_NAME}=="?*", ENV{DM_LV_LAYER}!="?*", SYMLINK+="$env{DM_VG_NAME}/$env{DM_LV_NAME}" + +LABEL="lvm_end" diff --git a/udev/12-dm-disk.rules b/udev/12-dm-disk.rules new file mode 100644 index 000000000..4b81420c7 --- /dev/null +++ b/udev/12-dm-disk.rules @@ -0,0 +1,30 @@ +# Udev rules for device-mapper devices. +# +# These rules create symlinks in /dev/disk directory. +# Symlinks that depend on probing filesystem type, +# label and uuid are created only if the device is not +# suspended. + +SUBSYSTEM!="block", GOTO="dm_end" +KERNEL!="dm-[0-9]*", GOTO="dm_end" +ACTION!="add|change", GOTO="dm_end" +ENV{DM_NAME}!="?*", GOTO="dm_end" + +# Normally, we operate on "change" events only. But when +# coldplugging, there's an "add" event present. We have to +# recognize this and do our actions in this particular +# situation, too. +ACTION=="add", ENV{STARTUP}!="1", GOTO="dm_end" + +SYMLINK+="disk/by-id/dm-name-$env{DM_NAME}" +ENV{DM_UUID}=="?*", SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}" + +ENV{DM_SUSPENDED}=="1", GOTO="dm_end" + +IMPORT{program}="vol_id --export $tempnode" +OPTIONS="link_priority=-100" +ENV{DM_LV_LAYER}=="?*", OPTIONS="link_priority=-90" +ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}" +ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}" + +LABEL="dm_end" diff --git a/udev/95-dm-notify.rules b/udev/95-dm-notify.rules new file mode 100644 index 000000000..236878f79 --- /dev/null +++ b/udev/95-dm-notify.rules @@ -0,0 +1,16 @@ +# Udev rules for device-mapper devices. +# +# These rules are responsible for sending a notification to a process +# waiting for completion of udev rules. The process is identified by +# a cookie value sent within "change" and "remove" events (the cookie +# value is set before by that process for every action requested). +# Also, it sets default permissions for DM devices if not set already. + +SUBSYSTEM!="block", GOTO="dm_end" +KERNEL!="dm-[0-9]*", GOTO="dm_end" +ACTION!="change|remove", GOTO="dm_end" + +ACTION=="change", OWNER:="root", GROUP:="root", MODE:="600" +ENV{DM_COOKIE}=="?*", RUN+="/sbin/dmsetup udevcomplete $env{DM_COOKIE}" + +LABEL="dm_end" diff --git a/udev/Makefile.in b/udev/Makefile.in index b547dd47a..73a43195d 100644 --- a/udev/Makefile.in +++ b/udev/Makefile.in @@ -14,3 +14,32 @@ srcdir = . top_srcdir = .. + +DM_RULES=10-dm.rules 12-dm-disk.rules 95-dm-notify.rules +LVM_RULES=11-lvm.rules +DM_DIR=$(shell grep "\#define DM_DIR" $(top_srcdir)/libdm/misc/dm-ioctl.h | awk '{print $$3}') + +CLEAN_TARGETS=10-dm.rules + +include $(top_srcdir)/make.tmpl + +%: %.in + $(SED) -e "s/(DM_DIR)/$(DM_DIR)/" $< >$@ + +install_lvm2: $(LVM_RULES) + @echo "Installing $(LVM_RULES) in $(udevdir)" + @for f in $(LVM_RULES); \ + do \ + $(RM) $(udevdir)/$$f; \ + $(INSTALL) -c -D $(OWNER) $(GROUP) -m 644 $$f $(udevdir)/$$f; \ + done + +install_device-mapper: $(DM_RULES) + @echo "Installing $(DM_RULES) in $(udevdir)" + @for f in $(DM_RULES); \ + do \ + $(RM) $(udevdir)/$$f; \ + $(INSTALL) -c -D $(OWNER) $(GROUP) -m 644 $$f $(udevdir)/$$f; \ + done + +install: install_lvm2 install_device-mapper