All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: Pawel Zmarzly <pzmarzly0@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] migration: fix parsing snapshots with x-ignore-shared flag
Date: Wed, 26 Nov 2025 14:21:53 -0500	[thread overview]
Message-ID: <aSdTUUbTbrTRQ3Ji@x1.local> (raw)
In-Reply-To: <87ldjtdk9t.fsf@suse.de>

On Wed, Nov 26, 2025 at 09:57:02AM -0300, Fabiano Rosas wrote:
> Pawel Zmarzly <pzmarzly0@gmail.com> writes:
> 
> > Snapshots made with mapped-ram and x-ignore-shared flags are
> > not parsed properly.
> >
> 
> I'd suggest some extra words to help people in the future (no need to
> resend, we can add it while merging):
> 
> "The ignore-shared feature adds and extra field in the stream, which
> needs to be consumed on the destination side. Even though mapped-ram has
> a fixed header format, the ignore-shared is part of the "generic" stream
> infomation so the mapped-ram code is currently skipping that be64 read
> which incorrectly offsets every subsequent read from the stream.
> 
> The current ignore-shared handling can simply be moved earlier in the
> code to encompass mapped-ram as well since the ignore-shared doubleword
> is the first one read when parsing the ramblock section of the stream."
> 
> > Co-authored-by: Peter Xu <peterx@redhat.com>
> > Signed-off-by: Pawel Zmarzly <pzmarzly0@gmail.com>
> 
> taking or leaving my additions:
> Reviewed-by: Fabiano Rosas <farosas@suse.de>
> 
> @Peter, we can probably merge this and deal with the rest of the
> ignore-shared situation later, right?

Yes agreed.

I queued this patch for -rc3 with Fabiano's update on the commit log,
thanks!

-- 
Peter Xu



      reply	other threads:[~2025-11-26 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 12:12 [PATCH v2] migration: fix parsing snapshots with x-ignore-shared flag Pawel Zmarzly
2025-11-26 12:57 ` Fabiano Rosas
2025-11-26 19:21   ` Peter Xu [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=aSdTUUbTbrTRQ3Ji@x1.local \
    --to=peterx@redhat.com \
    --cc=farosas@suse.de \
    --cc=pzmarzly0@gmail.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 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.