From: Stefano Brivio <sbrivio(a)redhat.com>
Check for errors setting REPAIR_OFF in flow_migrate_source_rollback().
In this situation there's not much we can do but die(), but this at least
should avoid hard to debug weirdness from continuing to operate with some
sockets in repair mode.
Signed-off-by: David Gibson <david(a)gibson.dropbear.id.au>
---
flow.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/flow.c b/flow.c
index 3fdc8881..dbe57082 100644
--- a/flow.c
+++ b/flow.c
@@ -912,9 +912,11 @@ static int flow_migrate_source_rollback(struct ctx *c, unsigned
max_flow,
debug("...roll back migration");
foreach_tcp_flow(i, flow, max_flow)
- tcp_flow_repair_off(c, &flow->tcp);
+ if (tcp_flow_repair_off(c, &flow->tcp))
+ die("Failed to roll back TCP_REPAIR mode");
- repair_flush(c);
+ if (repair_flush(c))
+ die("Failed to roll back TCP_REPAIR mode");
return ret;
}
--
2.48.1