qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: Orit Wasserman <owasserm@redhat.com>,
	aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix off-by-1 error in RAM migration code
Date: Fri, 02 Nov 2012 11:58:32 +0100	[thread overview]
Message-ID: <87625oi84n.fsf@elfo.mitica> (raw)
In-Reply-To: <20121102031508.GN27695@truffula.fritz.box> (David Gibson's message of "Fri, 2 Nov 2012 14:15:08 +1100")

David Gibson <dwg@au1.ibm.com> wrote:
> On Wed, Oct 31, 2012 at 01:08:16PM +0200, Orit Wasserman wrote:
>> On 10/31/2012 05:43 AM, David Gibson wrote:
>> > 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 <david@gibson.dropbear.id.au>
>> > ---
>> >  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;
>> > 
>> You are correct, good catch.
>> Reviewed-by: Orit Wasserman <owasserm@redhat.com>
>
> Juan,
>
> Sorry, forgot to CC you on the original mailing here, which I should
> have done.  This is a serious bug in the migration code and we should
> apply to mainline ASAP.

Reviewed-by: Juan Quintela <quintela@redhat.com> 

Good catch, I missunderstood the function when fixing a different bug,
and never undrestood why it fixed it.

Thanks, Juan.

  reply	other threads:[~2012-11-02 10:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  3:43 [Qemu-devel] [PATCH] Fix off-by-1 error in RAM migration code David Gibson
2012-10-31 11:08 ` Orit Wasserman
2012-11-02  3:15   ` David Gibson
2012-11-02 10:58     ` Juan Quintela [this message]
2012-11-03 15:00       ` David Gibson
2012-11-04 19:17         ` Juan Quintela
2012-11-05  0:17           ` David Gibson
2012-11-21  0:43       ` David Gibson

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=87625oi84n.fsf@elfo.mitica \
    --to=quintela@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=dwg@au1.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=qemu-devel@nongnu.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).