[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-changelog] [xen-unstable] tmem: fixup 2010 cleanup patch that breaks tmem save/restore
# HG changeset patch # User Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> # Date 1347365943 -7200 # Node ID 16e0392c6594b1757bbaa82076630a73d843229b # Parent 0520982a602a3ac06dd5bc573ddaff5edc9c6987 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> Committed-by: Jan Beulich <jbeulich@xxxxxxxx> --- diff -r 0520982a602a -r 16e0392c6594 xen/common/tmem.c --- a/xen/common/tmem.c Tue Sep 11 14:18:36 2012 +0200 +++ b/xen/common/tmem.c Tue Sep 11 14:19:03 2012 +0200 @@ -2419,6 +2419,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; @@ -2429,6 +2430,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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |