From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>, kvm <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Radim Krcmar <rkrcmar@redhat.com>
Cc: Wanpeng Li <wanpeng.li@hotmail.com>
Subject: Re: KVM: BUG during OOM on host
Date: Thu, 29 Jun 2017 19:14:27 +0200 [thread overview]
Message-ID: <1e45f831-4140-b59a-3237-8708ce19cbfd@redhat.com> (raw)
In-Reply-To: <CANRm+CysMtcSSUeaGJCd=s6OFXm=tDPMvqHT3D7VMTvvNRDg3g@mail.gmail.com>
On 29/06/2017 08:21, Wanpeng Li wrote:
> Hi all,
>
> When the OOM-Killer kills the guest which is running memory hog
> processes, there is tons of splatting as below: the page count reaches
> 0 before drop_spte. The splatting will disappear when disables THP on
> host.
Can you reproduce it in 4.10?
Thanks,
Paolo
> ------------[ cut here ]------------
> WARNING: CPU: 4 PID: 28317 at arch/x86/kvm/mmu.c:682
> mmu_spte_clear_track_bits+0x84/0x120 [kvm]
> CPU: 4 PID: 28317 Comm: kworker/4:2 Tainted: G B D W 4.12.0-rc7+ #29
> Workqueue: events mmput_async_fn
> task: ffff9465283c3280 task.stack: ffffacb0083b4000
> RIP: 0010:mmu_spte_clear_track_bits+0x84/0x120 [kvm]
> Call Trace:
> drop_spte+0x1a/0xb0 [kvm]
> mmu_page_zap_pte+0xcc/0xe0 [kvm]
> kvm_mmu_prepare_zap_page+0x81/0x4c0 [kvm]
> ? _raw_spin_lock+0x65/0x70
> kvm_mmu_invalidate_zap_all_pages+0x171/0x240 [kvm]
> kvm_arch_flush_shadow_all+0xe/0x10 [kvm]
> kvm_mmu_notifier_release+0x54/0x90 [kvm]
> ? kvm_mmu_notifier_release+0x5/0x90 [kvm]
> __mmu_notifier_release+0x65/0x100
> exit_mmap+0x168/0x180
> ? __khugepaged_exit+0xdb/0x140
> ? rcu_read_lock_sched_held+0x79/0x80
> ? kmem_cache_free+0x2f2/0x350
> mmput_async_fn+0x4c/0x140
> process_one_work+0x203/0x690
> worker_thread+0x4e/0x3b0
> kthread+0x117/0x150
>
> Regards,
> Wanpeng Li
>
next prev parent reply other threads:[~2017-06-29 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 6:21 Wanpeng Li
2017-06-29 17:14 ` Paolo Bonzini [this message]
2017-07-25 23:14 ` Wanpeng Li
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=1e45f831-4140-b59a-3237-8708ce19cbfd@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.com \
/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
all inboxes | Powered by JetHome®