[Xen-changelog] [xen-4.1-testing] tmem: fixup 2010 cleanup patch that breaks tmem save/restore

[Xen patchbot-4.1-testing <patchbot@xxxxxxx>]

# HG changeset patch
# User Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
# Date 1348568904 -7200
# Node ID 00ff640ebc7bd22b67b4c69f51dd44954c78dca8
# Parent  5a3829c943fff0295aa604a806009025c22dc9f3
tmem: fixup 2010 cleanup patch that breaks tmem save/restore

20918:a3fa6d444b25 "Fix domain reference leaks" (in Feb 2010, by Jan)
does some cleanup in addition to the leak fixes.  Unfortunately, that
cleanup inadvertently resulted in an incorrect fallthrough in a switch
statement which breaks tmem save/restore.

That broken patch was apparently applied to 4.0-testing and 4.1-testing
so those are broken as well.

What is the process now for requesting back-patches to 4.0 and 4.1?

(Side note: This does not by itself entirely fix save/restore in 4.2.)

Signed-off-by: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
xen-unstable changeset: 25859:16e0392c6594
xen-unstable date: Tue Sep 11 12:19:03 UTC 2012
---


diff -r 5a3829c943ff -r 00ff640ebc7b xen/common/tmem.c
--- a/xen/common/tmem.c Tue Sep 25 12:27:50 2012 +0200
+++ b/xen/common/tmem.c Tue Sep 25 12:28:24 2012 +0200
@@ -2422,6 +2422,7 @@ static NOINLINE int tmemc_save_subop(int
              break;
         tmh_copy_to_client_buf(buf, pool->uuid, 2);
         rc = 0;
+        break;
     case TMEMC_SAVE_END:
         if ( client == NULL )
             break;
@@ -2432,6 +2433,7 @@ static NOINLINE int tmemc_save_subop(int
                 pgp_free_from_inv_list(client,pgp);
         client->frozen = client->was_frozen;
         rc = 0;
+        break;
     }
     return rc;
 }

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog