From: Amit Shah <amit.shah@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: agraf@suse.de, quintela@redhat.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] Add section footers to detect corrupted migration streams
Date: Wed, 20 May 2015 12:43:33 +0530 [thread overview]
Message-ID: <20150520071333.GI15452@grmbl.mre> (raw)
In-Reply-To: <555B4520.7000109@redhat.com>
On (Tue) 19 May 2015 [08:13:52], Eric Blake wrote:
> On 05/19/2015 08:06 AM, Dr. David Alan Gilbert wrote:
>
> >> Does it let us detect a corrupted
> >> stream earlier in the process? Or is the main benefit that it gives
> >> better error messages at the point corruption is first detected?
> >
> > Both; there are two cases that often happen; both triggered by a section
> > reading too little or too much, and it gets back to the main loop and
> > we read the next byte:
> > 1) the next byte on the stream is a 0x00 - that's read as an end-of-migration
> > marker, we start the VM and you get a hung VM with no errors.
> >
> > 2) the next byte is between 0x01..0x04 - and it looks like a section header,
> > then we try and read the next few bytes to figure out which section;
> > this could a) result in an error saying it's an unknown section or
> > b) Happen to match a section ID and then get an error about a problem
> > in that section. In either case you don't get an error pointing to
> > the previous section which was the actual problem.
>
> Probably worth incorporating into the commit body then :)
How about docs/migration.txt? The 00/NN message gets lost..
Amit
next prev parent reply other threads:[~2015-05-20 7:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 11:29 [Qemu-devel] [PATCH 0/4] Add section footers to detect corrupted migration streams Dr. David Alan Gilbert (git)
2015-05-19 11:29 ` [Qemu-devel] [PATCH 1/4] Merge section header writing Dr. David Alan Gilbert (git)
2015-05-20 8:50 ` Juan Quintela
2015-05-19 11:29 ` [Qemu-devel] [PATCH 2/4] Disable section footers on older machine types Dr. David Alan Gilbert (git)
2015-05-20 8:52 ` Juan Quintela
2015-05-20 17:02 ` Dr. David Alan Gilbert
2015-05-19 11:29 ` [Qemu-devel] [PATCH 3/4] Add a protective section footer Dr. David Alan Gilbert (git)
2015-05-20 8:53 ` Juan Quintela
2015-05-19 11:29 ` [Qemu-devel] [PATCH 4/4] Teach analyze-migration.py about section footers Dr. David Alan Gilbert (git)
2015-05-19 13:51 ` [Qemu-devel] [PATCH 0/4] Add section footers to detect corrupted migration streams Eric Blake
2015-05-19 14:06 ` Dr. David Alan Gilbert
2015-05-19 14:13 ` Eric Blake
2015-05-19 14:28 ` Dr. David Alan Gilbert
2015-05-19 14:40 ` Eric Blake
2015-05-20 8:58 ` Juan Quintela
2015-05-20 7:13 ` Amit Shah [this message]
2015-05-20 7:18 ` Amit Shah
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=20150520071333.GI15452@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=agraf@suse.de \
--cc=dgilbert@redhat.com \
--cc=eblake@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).