Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kvm-ppc@vger.kernel.org
Subject: "PR" KVM kvm-spt cache bug
Date: Wed, 14 Mar 2012 08:07:25 +0000	[thread overview]
Message-ID: <1331712445.3105.118.camel@pasglop> (raw)

Hi Alex !

Saw that in my log today:

======================================BUG kvm-spt (Not tainted): Objects remaining on kmem_cache_close()
-----------------------------------------------------------------------------

INFO: Slab 0xc000000005a82470 objects1 used=6 fp=0xc00000010f382210 flags=0x4080
Call Trace:
[c0000001445439b0] [c00000000001100c] .show_stack+0x80/0x130 (unreliable)
[c000000144543a60] [c0000000000fe5bc] .slab_err+0x5c/0x68
[c000000144543b60] [c000000000102004] .kmem_cache_destroy+0x144/0x308
[c000000144543c40] [d00000000188a384] .kvmppc_mmu_hpte_sysexit+0x1c/0x28 [kvm]
[c000000144543cc0] [d000000001887ffc] .kvmppc_book3s_exit+0x10/0x2c [kvm]
[c000000144543d30] [c000000000094310] .SyS_delete_module+0x1cc/0x258
[c000000144543e30] [c000000000007720] syscall_exit+0x0/0x38
INFO: Object 0xc00000010f382b58 @offset)04
INFO: Object 0xc00000010f382f78 @offset960
INFO: Object 0xc00000010f383080 @offsetB24
INFO: Object 0xc00000010f383188 @offsetD88
INFO: Object 0xc00000010f383290 @offsetG52
INFO: Object 0xc00000010f3837b8 @offset`72
SLUB kvm-spt: kmem_cache_destroy called for cache that still has objects.
Call Trace:
[c000000144543ab0] [c00000000001100c] .show_stack+0x80/0x130 (unreliable)
[c000000144543b60] [c00000000010215c] .kmem_cache_destroy+0x29c/0x308
[c000000144543c40] [d00000000188a384] .kvmppc_mmu_hpte_sysexit+0x1c/0x28 [kvm]
[c000000144543cc0] [d000000001887ffc] .kvmppc_book3s_exit+0x10/0x2c [kvm]
[c000000144543d30] [c000000000094310] .SyS_delete_module+0x1cc/0x258
[c000000144543e30] [c000000000007720] syscall_exit+0x0/0x38

No more info ... yet. from what I can tell it happened only once.

Cheers,
Ben.



                 reply	other threads:[~2012-03-14  8:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1331712445.3105.118.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=kvm-ppc@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