From: Marcelo Tosatti <mtosatti@redhat.com>
To: Don Dupuis <dondster@gmail.com>, Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: kernel NULL pointer dereference/ kvm subsystem
Date: Mon, 8 Feb 2010 15:29:31 -0200 [thread overview]
Message-ID: <20100208172931.GA5315@amt.cnet> (raw)
In-Reply-To: <632b79000910060738l5ed0dd6ch60b4569d87d2ef0e@mail.gmail.com>
On Tue, Oct 06, 2009 at 09:38:05AM -0500, Don Dupuis wrote:
> Kernel 2.6.31.2
> x86 64bit
>
> Running numerous kvm linux guests and noticed this oops in messages
> file. This didn't occur in 2.6.30.6
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
> IP: [<ffffffffa01de29f>] kpit_elapsed+0x30/0x60 [kvm]
Fixed by ace1546487a0fe4634e3251067f8a32cb2cdc099.
Greg, can you please cherry pick to 2.6.31.stable?
TIA
next prev parent reply other threads:[~2010-02-08 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 14:38 kernel NULL pointer dereference/ kvm subsystem Don Dupuis
2010-02-08 17:29 ` Marcelo Tosatti [this message]
2010-02-08 19:09 ` Avi Kivity
2010-02-08 19:49 ` Rafael J. Wysocki
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=20100208172931.GA5315@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=dondster@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox