From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] migration: don't segfault on invalid input
Date: Sun, 17 Oct 2010 23:10:55 +0200 [thread overview]
Message-ID: <20101017211055.GA13854@redhat.com> (raw)
In-Reply-To: <1287349305.21691.17.camel@x201>
On Sun, Oct 17, 2010 at 03:01:45PM -0600, Alex Williamson wrote:
> On Sun, 2010-10-17 at 20:43 +0200, Michael S. Tsirkin wrote:
> > host_from_stream_offset returns NULL on error,
> > return error instead of trying to use that address,
> > to avoid segfault on invalid stream.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > arch_init.c | 5 +++++
> > 1 files changed, 5 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch_init.c b/arch_init.c
> > index e468c0c..bc7528d 100644
> > --- a/arch_init.c
> > +++ b/arch_init.c
> > @@ -116,6 +116,8 @@ static int ram_save_block(QEMUFile *f)
> >
> > if (!block)
> > block = QLIST_FIRST(&ram_list.blocks);
> > + if (!last_block)
> > + last_block = block;
> >
> > current_addr = block->offset + offset;
>
> NAK, last_block == block will cause us to set the continue flag on the
> first block. I assume you're trying to prevent the last_block->offset
> segv in the while test, but that should never happen. The only time
> last_block is NULL is at the beginning of stage 1, where all pages are
> dirty. At that point we should always enter the if {} block at the
> beginning of the do {} while, which breaks out rather than hitting the
> segv. We'll then set last_block for the next pass.
Sorry, sent this chunk in error.
> > @@ -390,6 +392,9 @@ int ram_load(QEMUFile *f, void *opaque, int version_id)
> > host = qemu_get_ram_ptr(addr);
> > else
> > host = host_from_stream_offset(f, addr, flags);
> > + if (!host) {
> > + return -EINVAL;
> > + }
> >
>
> This should also never happen since we've synchronized ramblocks at the
> beginning of migration, but probably a good idea to return an error.
> Thanks,
>
> Alex
prev parent reply other threads:[~2010-10-17 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 18:43 [Qemu-devel] [PATCH] migration: don't segfault on invalid input Michael S. Tsirkin
2010-10-17 21:01 ` [Qemu-devel] " Alex Williamson
2010-10-17 21:10 ` Michael S. Tsirkin [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=20101017211055.GA13854@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@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 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.