From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: dong <bauers@126.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Re: Re: [Bug 201699] New: kmemleak in memcg_create_kmem_cache
Date: Wed, 21 Nov 2018 11:52:23 +0300 [thread overview]
Message-ID: <20181121085223.dylxncsobzoyok4w@esperanza> (raw)
In-Reply-To: <6185b79c.9161.1672bd49ed1.Coremail.bauers@126.com>
On Mon, Nov 19, 2018 at 07:56:53PM +0800, dong wrote:
> Sorry, there's a leak indeed. The memory was leaking all the time and
> I tried to run command `echo 3 > /proc/sys/vm/drop_caches`, it didn't
> help.
>
> But when I delete the log files which was created by the failed
> systemd service, the leak(cached) memory was released. I suspect the
> leak is relevant to the inode objects.
What kind of filesystem is used for storing logs?
Also, I assume you use SLAB. It would be nice if you could try to
reproduce the issue with SLUB, because the latter exports information
about per memcg caches under /sys/kernel/slab/<cache-name>/cgroup. It
could shed the light on what kinds of objects are not freed after cgroup
destruction.
In case of SLAB you can try to monitor /proc/slabinfo to see which
caches are growing. Anyway, you'll probably have to turn off kmem cache
merging - see slab_nomerge boot options.
prev parent reply other threads:[~2018-11-21 8:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201699-27@https.bugzilla.kernel.org/>
2018-11-15 21:06 ` Andrew Morton
2018-11-16 2:23 ` dong
2018-11-16 3:04 ` dong
2018-11-16 3:37 ` dong
2018-11-16 17:50 ` Vladimir Davydov
2018-11-18 0:44 ` dong
2018-11-19 8:30 ` Vladimir Davydov
2018-11-19 10:24 ` Michal Hocko
2018-11-19 11:56 ` dong
2018-11-21 8:46 ` dong
2018-11-21 8:56 ` Vladimir Davydov
2018-11-21 9:06 ` dong
2018-11-21 9:10 ` Michal Hocko
2018-11-21 9:22 ` dong
2018-11-21 9:36 ` 段熊春
2018-11-21 16:27 ` Michal Hocko
2018-11-22 2:19 ` 段熊春
2018-11-22 7:32 ` Michal Hocko
2018-11-22 2:56 ` 段熊春
2018-11-22 7:34 ` Michal Hocko
2018-11-22 8:21 ` 段熊春
2018-11-23 6:54 ` 段熊春
2018-11-21 8:52 ` Vladimir Davydov [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=20181121085223.dylxncsobzoyok4w@esperanza \
--to=vdavydov.dev@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bauers@126.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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