From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: kvm_rmap_desc: Can't free all objects
Date: Thu, 11 Oct 2007 08:56:47 +0200 [thread overview]
Message-ID: <470DC92F.2000003@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A023648F4-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
> Avi:
> Time to time, I see this error message, any typo exist?
> thx,eddie
>
>
> slab error in kmem_cache_destroy(): cache `kvm_rmap_desc': Can't free
> all objects
>
> Call Trace:
> [<ffffffff8027c0fe>] kmem_cache_destroy+0x93/0xdc
> [<ffffffff88009125>] :kvm:kvm_mmu_module_exit+0x23/0x37
> [<ffffffff88010360>] :kvm:kvm_exit+0x26/0x31
> [<ffffffff8024f026>] sys_delete_module+0x1b4/0x1e5
> [<ffffffff8034eee3>] __up_write+0x14/0x108
> [<ffffffff8026d2a3>] sys_munmap+0x4b/0x58
> [<ffffffff8020b42e>] system_call+0x7e/0x83
>
I saw this yesterday and an debugging it now...
It's caused by the mmu not handling permissions changing on a pde correctly.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-11 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 6:37 kvm_rmap_desc: Can't free all objects Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A023648F4-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-11 6:56 ` Avi Kivity [this message]
[not found] ` <470DC92F.2000003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-11 13:31 ` Avi Kivity
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=470DC92F.2000003@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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