From: Michal Hocko <mhocko@kernel.org>
To: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: dong <bauers@126.com>, Johannes Weiner <hannes@cmpxchg.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <guroan@gmail.com>
Subject: Re: Re: [Bug 201699] New: kmemleak in memcg_create_kmem_cache
Date: Mon, 19 Nov 2018 11:24:28 +0100 [thread overview]
Message-ID: <20181119102428.GE22247@dhcp22.suse.cz> (raw)
In-Reply-To: <20181119083045.m5rhvbsze4h5l6jq@esperanza>
[Cc Roman - the email thread starts
http://lkml.kernel.org/r/20181115130646.6de1029eb1f3b8d7276c3543@linux-foundation.org]
On Mon 19-11-18 11:30:45, Vladimir Davydov wrote:
> On Sun, Nov 18, 2018 at 08:44:14AM +0800, dong wrote:
> > First of all,I can see memory leak when I run a??free -ga?? command.
>
> This doesn't mean there's a leak. The kernel may postpone freeing memory
> until there's memory pressure. In particular cgroup objects are not
> released until there are objects allocated from the corresponding kmem
> caches. Those objects may be inodes or dentries, which are freed lazily.
> Looks like restarting a service causes recreation of a memory cgroup and
> hence piling up dead cgroups. Try to drop caches.
This seems similar to what Roman was looking recently. All the fixes
should be merged in the current Linus tree IIRC.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-11-19 10:24 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 ` [Bug 201699] New: kmemleak in memcg_create_kmem_cache 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 [this message]
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 ` Re: " Vladimir Davydov
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=20181119102428.GE22247@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bauers@126.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=guroan@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.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;
as well as URLs for NNTP newsgroup(s).