From: Olaf Hering <olaf@aepfle.de>
To: Tim Deegan <tim@xen.org>
Cc: Eddie Dong <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
xen-devel@lists.xen.org
Subject: Re: crash in nvmx_vcpu_destroy
Date: Thu, 21 Feb 2013 15:19:19 +0100 [thread overview]
Message-ID: <20130221141919.GA20093@aepfle.de> (raw)
In-Reply-To: <20130221111000.GG24051@ocelot.phlegethon.org>
On Thu, Feb 21, Tim Deegan wrote:
> At 11:01 +0000 on 21 Feb (1361444479), Tim Deegan wrote:
> > (Cc'ing the vmx maintainers)
> >
> > At 15:58 +0100 on 20 Feb (1361375903), Olaf Hering wrote:
> > > while doing "while xm migrate --live domU localhost;do sleep 1;done" I
> > > just got the crash shown below. And it can be reproduced.
> > >
> > > The guest has 2 vcpus and 512mb, it runs pvops 3.7.9
> >
> > Anything interesting printed before the crash? My best guess by code
> > inspection is that nvmx->launched_list never got initialized, because of
> > some failure in vcpu init.
> >
> > Also, if you have the xen-syms for this image, can you extract a
> > file/line-number for the crashing %rip (ffff82c4c01dd197)?
> > I'd expect it to be vvmx.c:150 or thereabouts.
> >
> > And thirdly, can you try the attached patch?
>
> Oops - not sure what I tested before , but that one doesn't even
> compile! Try this instead.
This patch fixes the crash for me. Thanks.
Olaf
> diff --git a/xen/arch/x86/hvm/vmx/vvmx.c b/xen/arch/x86/hvm/vmx/vvmx.c
> index 4f3f94d..5d00ff7 100644
> --- a/xen/arch/x86/hvm/vmx/vvmx.c
> +++ b/xen/arch/x86/hvm/vmx/vvmx.c
> @@ -147,10 +147,13 @@ void nvmx_vcpu_destroy(struct vcpu *v)
> nvcpu->nv_n2vmcx = NULL;
> }
>
> - list_for_each_entry_safe(item, n, &nvmx->launched_list, node)
> + if ( nvmx->launched_list.next )
> {
> - list_del(&item->node);
> - xfree(item);
> + list_for_each_entry_safe(item, n, &nvmx->launched_list, node)
> + {
> + list_del(&item->node);
> + xfree(item);
> + }
> }
>
> if ( v->arch.hvm_vmx.vmread_bitmap )
next prev parent reply other threads:[~2013-02-21 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 14:58 crash in nvmx_vcpu_destroy Olaf Hering
2013-02-21 10:49 ` Olaf Hering
2013-02-21 11:03 ` Jan Beulich
2013-02-21 11:29 ` Jan Beulich
2013-02-21 11:08 ` Tim Deegan
2013-02-21 11:01 ` Tim Deegan
2013-02-21 11:10 ` Tim Deegan
2013-02-21 14:19 ` Olaf Hering [this message]
2013-02-21 14:22 ` Tim Deegan
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=20130221141919.GA20093@aepfle.de \
--to=olaf@aepfle.de \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.