From dd180cb136d6b2193a58ea0de23b8a7942ca6f36 Mon Sep 17 00:00:00 2001 From: NeilBrown Date: Fri, 5 May 2017 15:16:15 +1000 Subject: [PATCH] Fix typo in new udev rule. As pointed out by Peter Rajnoha, the correct usage in udev is TEST=="file", not TEST="file". Also improve a related comment which was a bit informal. Reported-by: Peter Rajnoha Fixes: cd6cbb08c458 ("Create: tell udev md device is not ready when first created.") Signed-off-by: NeilBrown Signed-off-by: Jes Sorensen --- lib.c | 2 +- udev-md-raid-creating.rules | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lib.c b/lib.c index 7e44b1f..be093e8 100644 --- a/lib.c +++ b/lib.c @@ -165,7 +165,7 @@ char *fd2devnm(int fd) /* When we create a new array, we don't want the content to * be immediately examined by udev - it is probably meaningless. - * So create /run/mdadm/creating-FOO and expect that a udev + * So create /run/mdadm/creating-mdXXX and expect that a udev * rule will noticed this and act accordingly. */ static char block_path[] = "/run/mdadm/creating-%s"; diff --git a/udev-md-raid-creating.rules b/udev-md-raid-creating.rules index 2be466b..9bef8d1 100644 --- a/udev-md-raid-creating.rules +++ b/udev-md-raid-creating.rules @@ -4,4 +4,4 @@ # the array is not "ready" and we should make sure the # content is ignored. -KERNEL=="md*", TEST="/run/mdadm/creating-$kernel", ENV{SYSTEMD_READY}="0" +KERNEL=="md*", TEST=="/run/mdadm/creating-$kernel", ENV{SYSTEMD_READY}="0"