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