From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TTPBg-0000RI-AD for qemu-devel@nongnu.org; Tue, 30 Oct 2012 23:41:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TTPBf-00082L-8E for qemu-devel@nongnu.org; Tue, 30 Oct 2012 23:41:52 -0400 Received: from ozlabs.org ([203.10.76.45]:47076) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TTPBe-00080V-TS for qemu-devel@nongnu.org; Tue, 30 Oct 2012 23:41:51 -0400 From: David Gibson Date: Wed, 31 Oct 2012 14:43:08 +1100 Message-Id: <1351654988-13165-1-git-send-email-david@gibson.dropbear.id.au> Subject: [Qemu-devel] [PATCH] Fix off-by-1 error in RAM migration code List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: aliguori@us.ibm.com Cc: qemu-devel@nongnu.org, David Gibson The code for migrating (or savevm-ing) memory pages starts off by creating a dirty bitmap and filling it with 1s. Except, actually, because bit addresses are 0-based it fills every bit except bit 0 with 1s and puts an extra 1 beyond the end of the bitmap, potentially corrupting unrelated memory. Oops. This patch fixes it. Signed-off-by: David Gibson --- arch_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch_init.c b/arch_init.c index e6effe8..b75a4c5 100644 --- a/arch_init.c +++ b/arch_init.c @@ -568,7 +568,7 @@ static int ram_save_setup(QEMUFile *f, void *opaque) int64_t ram_pages = last_ram_offset() >> TARGET_PAGE_BITS; migration_bitmap = bitmap_new(ram_pages); - bitmap_set(migration_bitmap, 1, ram_pages); + bitmap_set(migration_bitmap, 0, ram_pages); migration_dirty_pages = ram_pages; bytes_transferred = 0; -- 1.7.10.4