572a44
From 24888798c1c90dbdc7ab0aa0b57f2196066712c4 Mon Sep 17 00:00:00 2001
572a44
From: Lennart Poettering <lennart@poettering.net>
572a44
Date: Wed, 16 Oct 2013 02:49:54 +0200
572a44
Subject: [PATCH] rules: expose loop block devices to systemd
572a44
572a44
Since the kernel no longer exposes a large number of "dead" loop devices
572a44
it is OK to expose them now in systemd, so let's do that. This has the
572a44
benefit that mount dependencies on loop devices start to work.
572a44
---
572a44
 rules/99-systemd.rules.in | 6 +++---
572a44
 1 file changed, 3 insertions(+), 3 deletions(-)
572a44
572a44
diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in
572a44
index bbb7d0c..3c99475 100644
572a44
--- a/rules/99-systemd.rules.in
572a44
+++ b/rules/99-systemd.rules.in
572a44
@@ -11,12 +11,12 @@ SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*", TAG+="systemd"
572a44
 
572a44
 KERNEL=="vport*", TAG+="systemd"
572a44
 
572a44
-SUBSYSTEM=="block", KERNEL!="ram*|loop*", TAG+="systemd"
572a44
-SUBSYSTEM=="block", KERNEL!="ram*|loop*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
572a44
+SUBSYSTEM=="block", KERNEL!="ram*", TAG+="systemd"
572a44
+SUBSYSTEM=="block", KERNEL!="ram*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
572a44
 
572a44
 # Ignore encrypted devices with no identified superblock on it, since
572a44
 # we are probably still calling mke2fs or mkswap on it.
572a44
-SUBSYSTEM=="block", KERNEL!="ram*|loop*", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0"
572a44
+SUBSYSTEM=="block", KERNEL!="ram*", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0"
572a44
 
572a44
 # Ignore raid devices that are not yet assembled and started
572a44
 SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", TEST!="md/array_state", ENV{SYSTEMD_READY}="0"