From: Avi Kivity <avi@qumranet.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "\"S.Çağlar Onur\"" <caglar@pardus.org.tr>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [GIT PULL][RESEND] Late KVM Updates for the 2.6.23 merge window
Date: Sat, 21 Jul 2007 08:58:12 +0300 [thread overview]
Message-ID: <46A1A074.6050803@qumranet.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707201633390.27249@woody.linux-foundation.org>
Linus Torvalds wrote:
> On Sat, 21 Jul 2007, S.Çağlar Onur wrote:
>
>> With Linus's latest git, shutting down a guest (fired with -smp 2 -m 512) sometimes
>> ends up like [1], this occured as soon as qemu window closed.
>>
>> [1] http://cekirdek.pardus.org.tr/~caglar/kvm/dmesg.latest
>>
>
> [ 737.460654] Bad page state in process 'qemu-kvm'
> [ 737.460656] page:f5e68000 flags:0xea020000 mapping:00000000 mapcount:2 count:0
> [ 737.460657] Trying to fix it up, but a reboot is needed
> [ 737.460659] Backtrace:
> [ 737.460691] [<c0159e70>] bad_page+0x64/0x8e
> [ 737.460733] [<c015a7ee>] free_hot_cold_page+0x68/0x15a
>
> That's the "free_pages_check()", and in particular it seems to be
> "page_mapcount()" being non-zero that triggered that thing.
>
> So it looks like something in KVM isn't coherent about the mapping vs the
> usage counters..
>
>
Far more prosaic. It calls __free_page() on the cleanup path with the
page's virtual address instead of the struct page. I guess
__free_page() is happy with a zeroed out blob, which is the most likely
contents.
Trivial patch shortly.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2007-07-21 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 17:32 [GIT PULL][RESEND] Late KVM Updates for the 2.6.23 merge window Avi Kivity
2007-07-20 23:21 ` [kvm-devel] " S.Çağlar Onur
2007-07-20 23:37 ` Linus Torvalds
2007-07-21 5:58 ` Avi Kivity [this message]
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=46A1A074.6050803@qumranet.com \
--to=avi@qumranet.com \
--cc=caglar@pardus.org.tr \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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