From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 208081] New: Memory leak in kvm_async_pf_task_wake
Date: Sat, 06 Jun 2020 00:35:39 +0000 [thread overview]
Message-ID: <bug-208081-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208081
Bug ID: 208081
Summary: Memory leak in kvm_async_pf_task_wake
Product: Virtualization
Version: unspecified
Kernel Version: 5.6.14
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: sites+kernel@d.sb
Regression: No
I have several KVM virtual servers at a number of hosting providers. On just
one of them, the unreclaimable slab memory is growing linearly over time, until
it hits a maximum (when the server's memory is 100% allocated). All the memory
is allocated in kmalloc-64 slabs.
After enabling slab debugging using slub_debug=U,
/sys/kernel/slab/kmalloc-64/alloc_calls says that most of the allocations are
coming from kvm_async_pf_task_wake
This looks very similar to this blog post:
https://darkimmortal.com/debian-10-kernel-slab-memory-leak/. Also see my post
on ServerFault:
https://serverfault.com/questions/1020241/debugging-kmalloc-64-slab-allocations-memory-leak
Any suggestions on how to debug this? It seems like it could be a kernel bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-06-06 0:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 0:35 bugzilla-daemon [this message]
2020-06-06 0:37 ` [Bug 208081] Memory leak in kvm_async_pf_task_wake bugzilla-daemon
2020-06-08 0:46 ` bugzilla-daemon
2020-06-09 7:17 ` bugzilla-daemon
2020-06-09 13:00 ` bugzilla-daemon
2020-06-09 17:09 ` bugzilla-daemon
2020-06-11 1:03 ` bugzilla-daemon
2023-01-24 7:54 ` bugzilla-daemon
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=bug-208081-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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