From 9eafc65cb4a7d8de0a500cb71a0ba02863dc6a12 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Fri, 20 Apr 2018 16:47:46 +0200 Subject: [PATCH] udev: don't call udev-block-add-change for devices excluded by other rules The script call is quite expensive (it does multiple things, including checking device-mapper, qubesdb etc). Don't call it for devices we (or else) already excluded earlier. This is the most relevant for dom0, where udev "change" event is triggered quite often, for multiple LVM volumes - all excluded, because being VM's disks. --- udev/udev-qubes-block.rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/udev/udev-qubes-block.rules b/udev/udev-qubes-block.rules index 8d3a3af..cbb070a 100644 --- a/udev/udev-qubes-block.rules +++ b/udev/udev-qubes-block.rules @@ -10,6 +10,9 @@ KERNEL=="xvda|xvdb|xvdc*|xvdd", ENV{UDISKS_IGNORE}="1" # Skip xen-blkfront devices ENV{MAJOR}=="202", GOTO="qubes_block_end" +# skip devices excluded elsewhere +ENV{DM_UDEV_DISABLE_DISK_RULES_FLAG}=="1", GOTO="qubes_block_end" + # Skip device-mapper devices KERNEL=="dm-*", ENV{DM_NAME}=="snapshot-*", GOTO="qubes_block_end" KERNEL=="dm-*", ENV{DM_NAME}=="origin-*", GOTO="qubes_block_end"