From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: [PATCH for 4.6 v2 5/5] libxc: add assertion to avoid setting same bit more than once
Date: Sat, 5 Sep 2015 00:59:27 +0100 [thread overview]
Message-ID: <1441411167-32440-6-git-send-email-wei.liu2@citrix.com> (raw)
In-Reply-To: <1441411167-32440-1-git-send-email-wei.liu2@citrix.com>
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
tools/libxc/xc_sr_restore.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/libxc/xc_sr_restore.c b/tools/libxc/xc_sr_restore.c
index 924dd55..f48e7fc 100644
--- a/tools/libxc/xc_sr_restore.c
+++ b/tools/libxc/xc_sr_restore.c
@@ -181,6 +181,7 @@ static int pfn_set_populated(struct xc_sr_context *ctx, xen_pfn_t pfn)
ctx->restore.max_populated_pfn = new_max;
}
+ assert(!test_bit(pfn, ctx->restore.populated_pfns));
set_bit(pfn, ctx->restore.populated_pfns);
return 0;
--
2.1.4
prev parent reply other threads:[~2015-09-05 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 23:59 [PATCH for 4.6 v2 0/5] Migration v2 fix Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 1/5] libxc: clearer migration v2 debug message Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 2/5] libxc: migration v2 prefix Memory -> Frames Wei Liu
2015-09-06 16:23 ` Andrew Cooper
2015-09-06 19:21 ` Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 3/5] libxc: fix indentation Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 4/5] libxc: don't populate same pfn more than once in populate_pfns Wei Liu
2015-09-06 16:25 ` Andrew Cooper
2015-09-04 23:59 ` Wei Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1441411167-32440-6-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).