From b045f4fe9a0fc433554e99324fa3c2598f383d06 Mon Sep 17 00:00:00 2001 From: Peter Rajnoha Date: Thu, 12 Aug 2010 13:07:08 +0000 Subject: Reinstate detection of inappropriate uevent with DISK_RO set and suppress it. We still need to detect this one! We're not so strict with CHANGE events as with the ADD events while applying filters in the rules so this one would pass and it would process the rules prematurely (because it appears *before* the actual CHANGE event used when resuming a DM device while setting read-only state at the same time). --- udev/10-dm.rules.in | 3 +++ 1 file changed, 3 insertions(+) (limited to 'udev') diff --git a/udev/10-dm.rules.in b/udev/10-dm.rules.in index 5d2a22b4..c40805a8 100644 --- a/udev/10-dm.rules.in +++ b/udev/10-dm.rules.in @@ -42,6 +42,9 @@ ENV{DM_COOKIE}=="?*", IMPORT{program}="$env{DM_SBIN_PATH}/dmsetup udevflags $env # is not recommended. ACTION!="add|change", GOTO="dm_end" +# 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 -- cgit