kdump-utils/0003-Fix-the-way-to-tell-if-there-is-a-need-to-set-up-net.patch
Coiby Xu 647ca6bdfa Support dumping to NVMe/TCP configured using NVMe Boot Firmware Table
Resolves: RHEL-100907
Upstream: kdump-utils
Conflict: None

Signed-off-by: Coiby Xu <coxu@redhat.com>
2025-07-28 17:13:58 +08:00

43 lines
1.5 KiB
Diff

From 1d7bdb507217adeaced260b1d11d8dc16146c5cb Mon Sep 17 00:00:00 2001
From: Coiby Xu <coxu@redhat.com>
Date: Fri, 30 May 2025 11:10:44 +0800
Subject: [PATCH] Fix the way to tell if there is a need to set up network
Related: https://issues.redhat.com/browse/RHEL-33413
Currently, dumping vmcore to a NVMe TCP target fails. The dracut nvmf is
supposed to be fully responsible for setting up the network and there is
no need for the involvement of the kdump dracut modle. However currently
_get_kdump_netifs returns " " even there is no NIC to be set up so the
kdump dracut module will be mislead to set up network and even install a
NetworkManager configuration file that stops all NICs from brought up by
NM. Thus NVMe TCP target fails to be set up because of network failure.
Fix _get_kdump_netifs so empty result instead of " " will be returned.
Fixes: 224d3102 ("Support setting up Open vSwitch (Ovs) Bridge network")
Signed-off-by: Coiby Xu <coxu@redhat.com>
---
dracut/99kdumpbase/module-setup.sh | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/dracut/99kdumpbase/module-setup.sh b/dracut/99kdumpbase/module-setup.sh
index bd29eaa5..d71b28ce 100755
--- a/dracut/99kdumpbase/module-setup.sh
+++ b/dracut/99kdumpbase/module-setup.sh
@@ -11,7 +11,10 @@ _save_kdump_netifs() {
}
_get_kdump_netifs() {
- echo -n "${!unique_netifs[@]} ${!ovs_unique_netifs[@]}"
+ local -a _all_netifs
+
+ _all_netifs=("${!unique_netifs[@]}" "${!ovs_unique_netifs[@]}")
+ echo -n "${_all_netifs[@]}"
}
kdump_module_init() {
--
2.50.1