[prev in list] [next in list] [prev in thread] [next in thread]
List: netcf-devel
Subject: [netcf-devel] [PATCH 2/4] ifup/ifdown: make sure errors from run1 are propagated
From: lutter () redhat ! com (David Lutterkort)
Date: 2009-09-15 17:54:27
Message-ID: 1253037269-6302-3-git-send-email-lutter () redhat ! com
[Download RAW message or body]
---
src/drv_initscripts.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/src/drv_initscripts.c b/src/drv_initscripts.c
index e17d834..e928962 100644
--- a/src/drv_initscripts.c
+++ b/src/drv_initscripts.c
@@ -978,6 +978,7 @@ int drv_if_up(struct netcf_if *nif) {
}
}
run1(ncf, ifup, nif->name);
+ ERR_BAIL(ncf);
result = 0;
error:
free_matches(nslaves, &slaves);
@@ -992,6 +993,7 @@ int drv_if_down(struct netcf_if *nif) {
int result = -1;
run1(ncf, ifdown, nif->name);
+ ERR_BAIL(ncf);
if (is_bridge(ncf, nif->name)) {
/* Bring up bridge slaves after the bridge */
nslaves = bridge_slaves(ncf, nif->name, &slaves);
--
1.6.2.5
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic