From: Dmitry Antipov <dmantipov@yandex.ru>
To: linux-mm@kvack.org
Cc: lvc-project@linuxtesting.org
Subject: Debugging memory leak which depends on CPU topology
Date: Wed, 11 Sep 2024 19:37:33 +0300 [thread overview]
Message-ID: <c25c7ec0-aa15-4219-b2bd-782ac16db4ae@yandex.ru> (raw)
Hello,
are there any hints for debugging kernel memory leak which seems
depends on CPU topology? There is a syzbot reproducer which causes
an OOM killer invocation nearly in a minute when running in a QEMU
VM with '-m 8G -smp 4,sockets=4,cores=1' but not with
'-m 8G -smp 8,sockets=4,cores=2'. To whom it may be interesting,
the one is https://syzkaller.appspot.com/text?tag=ReproC&x=10b60342980000,
and it produces an extremely high pressure on 'net_hotdata.skbuff_cache'
and 'net_hotdata.skb_small_head_cache'.
Thanks in advance,
Dmitry
reply other threads:[~2024-09-11 16:37 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=c25c7ec0-aa15-4219-b2bd-782ac16db4ae@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=linux-mm@kvack.org \
--cc=lvc-project@linuxtesting.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