File kdump-Dont-exit-even-if-initrd-is-not-built.patch of Package kdump.17231

From 086068496508087b68029ae31a93ed5d3e4ac2cb Mon Sep 17 00:00:00 2001
From: Ankit Kumar <ankit@linux.vnet.ibm.com>
Date: Mon, 7 Aug 2017 20:35:04 +0530
Subject: Don't exit even if initrd is not built
References: bsc#1047781, bsc#1073972, bsc#1081864
Upstream: v0.8.17
Git-commit: 086068496508087b68029ae31a93ed5d3e4ac2cb

In case where there is no change in kdump config, new initrd won't be
built. Restarting kdump.service in above case exits as initrd is same
as older. As control doesn't proceed further, it fails to enable dump
configuration.

This patch fixes above mentioned issue by proceeding further and enabling
dump configuration.

Signed-off-by: Ankit Kumar <ankit@linux.vnet.ibm.com>
Acked-by: Michal Suchanek <msuchanek@suse.de>
---
 init/load.sh |   10 ----------
 1 file changed, 10 deletions(-)

--- a/init/load.sh
+++ b/init/load.sh
@@ -305,17 +305,7 @@ fi
 
 find_kernel || exit 6
 if [ "$1" = "--update" ] ; then
-    before=$(stat -c %Y $kdump_initrd 2> /dev/null)
     rebuild_kdumprd || exit 1
-    after=$(stat -c %Y $kdump_initrd)
-
-    # If the initial ram disk was not updated,
-    # do not execute kexec again. This script
-    # is called from kdump.service and
-    # kdump-rebuild-initrd.service.
-    if [ "$before" = "$after" ] ; then
-        exit 0
-    fi
 fi
 
 if [ "$KDUMP_FADUMP" = "yes" ] ; then