From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [PATCH] migration: Fix a potential guest memory corruption
Date: Tue, 11 Oct 2022 12:05:43 +0100 [thread overview]
Message-ID: <Y0VOBwuMrdMwSUo+@work-vm> (raw)
In-Reply-To: <20220919093237.2219892-1-zhenzhong.duan@intel.com>
* Zhenzhong Duan (zhenzhong.duan@intel.com) wrote:
Hi,
> Imagine a rare case, after a dirty page is sent to compression threads's
> ring, dirty bitmap sync trigger right away and mark the same page dirty
> again and sent. Then the new page may be overwriten by stale page in
> compression threads's ring in the destination.
Yes, I think we had a similar problem in multifd.
> So we need to ensure there is only one copy of the same dirty page either
> by flushing the ring after every bitmap sync or avoiding processing same
> dirty page continuously.
>
> I choose the 2nd which avoids the time consuming flush operation.
I'm not sure this guarantees it; it makes it much less likely but if
only a few pages are dirtied and you have lots of threads, I think the
same thing could still happy.
I think you're going to need to flush the ring after each sync.
Dave
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> migration/ram.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index dc1de9ddbc68..67b2035586bd 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -1551,7 +1551,7 @@ static bool find_dirty_block(RAMState *rs, PageSearchStatus *pss, bool *again)
> pss->postcopy_requested = false;
> pss->postcopy_target_channel = RAM_CHANNEL_PRECOPY;
>
> - pss->page = migration_bitmap_find_dirty(rs, pss->block, pss->page);
> + pss->page = migration_bitmap_find_dirty(rs, pss->block, pss->page + 1);
> if (pss->complete_round && pss->block == rs->last_seen_block &&
> pss->page >= rs->last_page) {
> /*
> @@ -1564,7 +1564,7 @@ static bool find_dirty_block(RAMState *rs, PageSearchStatus *pss, bool *again)
> if (!offset_in_ramblock(pss->block,
> ((ram_addr_t)pss->page) << TARGET_PAGE_BITS)) {
> /* Didn't find anything in this RAM Block */
> - pss->page = 0;
> + pss->page = -1;
> pss->block = QLIST_NEXT_RCU(pss->block, next);
> if (!pss->block) {
> /*
> @@ -2694,7 +2694,7 @@ static void ram_state_reset(RAMState *rs)
> {
> rs->last_seen_block = NULL;
> rs->last_sent_block = NULL;
> - rs->last_page = 0;
> + rs->last_page = -1;
> rs->last_version = ram_list.version;
> rs->xbzrle_enabled = false;
> postcopy_preempt_reset(rs);
> @@ -2889,7 +2889,7 @@ void ram_postcopy_send_discard_bitmap(MigrationState *ms)
> /* Easiest way to make sure we don't resume in the middle of a host-page */
> rs->last_seen_block = NULL;
> rs->last_sent_block = NULL;
> - rs->last_page = 0;
> + rs->last_page = -1;
>
> postcopy_each_ram_send_discard(ms);
>
> --
> 2.25.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2022-10-11 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 9:32 [PATCH] migration: Fix a potential guest memory corruption Zhenzhong Duan
2022-10-11 11:05 ` Dr. David Alan Gilbert [this message]
2022-10-17 2:17 ` Duan, Zhenzhong
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=Y0VOBwuMrdMwSUo+@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhenzhong.duan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.