public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Tobias Diedrich <ranma+kernel@tdiedrich.de>,
	Chris Wright <chrisw@sous-sol.org>, Avi Kivity <avi@qumranet.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org, "Roedel,
	Joerg" <Jo
Subject: Re: kvm: unable to handle kernel NULL pointer dereference
Date: Thu, 5 Jun 2008 11:34:47 -0700	[thread overview]
Message-ID: <20080605183447.GL30402@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080605182847.GA12176@yamamaya.is-a-geek.org>

* Tobias Diedrich (ranma+kernel@tdiedrich.de) wrote:
> PM: Creating hibernation image: 
> PM: Need to copy 126181 pages
> PM: Normal pages needed: 126181 + 1024 + 38, available pages: 397721
> x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> svm_cpu_init: svm_data is NULL on 0

Yeah, this is broken.  What happens is:

suspend:
  hardware_disable
    svm_hardware_disable
      kfree(svm_data)
      per_cpu(svm_data) = NULL

resume:
  hardware_enable
    svm_hardware_enable
      if(!svm_data) printk("svm_cpu_init: svm_data is NULL on 0")

at this point it is broken.

Same would happen on an SMP box by simply doing offline/online of a CPU.
This is definitely busted, looking into a patch.

thanks,
-chris

  reply	other threads:[~2008-06-05 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01  8:48 kvm: unable to handle kernel NULL pointer dereference Tobias Diedrich
2008-06-04 10:41 ` Avi Kivity
2008-06-04 18:10   ` Tobias Diedrich
2008-06-05  4:25     ` Chris Wright
2008-06-05  6:09       ` Tobias Diedrich
2008-06-05  7:27         ` Chris Wright
2008-06-05 18:28           ` Tobias Diedrich
2008-06-05 18:34             ` Chris Wright [this message]
2008-06-29 18:02               ` Tobias Diedrich
2008-06-29 18:28                 ` [PATCH] " Tobias Diedrich

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=20080605183447.GL30402@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranma+kernel@tdiedrich.de \
    /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