qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Fix xbzrle vs last_sent_block update
Date: Thu, 10 Dec 2015 16:53:17 +0000	[thread overview]
Message-ID: <CAFEAcA-CU2eMCQH4WNbMA5k+eO3pWfwkdFjzs=XVsDY73Fa_oA@mail.gmail.com> (raw)
In-Reply-To: <1449765106-6528-1-git-send-email-dgilbert@redhat.com>

On 10 December 2015 at 16:31, Dr. David Alan Gilbert (git)
<dgilbert@redhat.com> wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> My fix (84e7b80a) replaced the last_sent_block update that I'd
> removed earlier; however it was too aggressive in the xbzrle case.
>
> save_xbzrle_page might return '0' to mean that the page didn't
> need sending since it was the same as the last sent version;
> in this case we can't update 'last_sent_block' since we didn't
> actually send it.
>
> Symptom: 'Illegal RAM offset 1018000' as we try and send a page
>         to the wrong RAMBlock;  potentially that could be a data
>         corruption if you were really unlucky.
>
> Fixes: 84e7b80a05c0c44b90533c6cd2f1db5c932ccf77
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>  migration/ram.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 1eb155a..0490f00 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -716,6 +716,9 @@ static int save_zero_page(QEMUFile *f, RAMBlock *block, ram_addr_t offset,
>   * ram_save_page: Send the given page to the stream
>   *
>   * Returns: Number of pages written.
> + *          < 0 - error
> + *          >=0 - Number of pages written - this might legally be 0
> + *                if xbzrle noticed the page was the same.
>   *
>   * @f: QEMUFile where to send the data
>   * @block: block that contains the page we want to send
> @@ -1249,7 +1252,13 @@ static int ram_save_target_page(MigrationState *ms, QEMUFile *f,
>          if (unsentmap) {
>              clear_bit(dirty_ram_abs >> TARGET_PAGE_BITS, unsentmap);
>          }
> -        last_sent_block = block;
> +        /* Only update last_sent_block if a block was actually sent; xbzrle
> +         * might have decided the page was identical so didn't bother writing
> +         * to the stream.
> +         */
> +        if (res > 0) {
> +            last_sent_block = block;
> +        }
>      }
>
>      return res;

This sounds like we should probably put this into 2.5; I'm happy
to do so if it gets review by tomorrow afternoon and Juan/Amit
agree.

thanks
-- PMM

  reply	other threads:[~2015-12-10 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 16:31 [Qemu-devel] [PATCH] Fix xbzrle vs last_sent_block update Dr. David Alan Gilbert (git)
2015-12-10 16:53 ` Peter Maydell [this message]
2015-12-11 12:25   ` Juan Quintela
2015-12-11 12:52     ` Peter Maydell
2015-12-11 13:15       ` Peter Maydell
2015-12-11 12:24 ` Juan Quintela

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='CAFEAcA-CU2eMCQH4WNbMA5k+eO3pWfwkdFjzs=XVsDY73Fa_oA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).