migration: If there is one error, it makes no sense to continue
authorJuan Quintela <quintela@redhat.com>
Wed, 23 Feb 2011 19:17:45 +0000 (20:17 +0100)
committerJuan Quintela <quintela@redhat.com>
Thu, 20 Oct 2011 11:23:51 +0000 (13:23 +0200)
Once there, add a comment about what each error mean.

Signed-off-by: Juan Quintela <quintela@redhat.com>
buffered_file.c

index 486af575d59cd8320f5b377ad516752811b139cf..94ecbbcea1640153db16cc0f93366eaa26d2cc9d 100644 (file)
@@ -189,13 +189,19 @@ static int buffered_close(void *opaque)
     return ret;
 }
 
+/*
+ * The meaning of the return values is:
+ *   0: We can continue sending
+ *   1: Time to stop
+ *  -1: There has been an error
+ */
 static int buffered_rate_limit(void *opaque)
 {
     QEMUFileBuffered *s = opaque;
 
-    if (s->has_error)
-        return 0;
-
+    if (s->has_error) {
+        return -1;
+    }
     if (s->freeze_output)
         return 1;