linux-kernel - Re: [PATCH] mm: memcg: expose mem_cgroup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALvZod5gy8iw-Va7-Gzyqv1xVkTGhU3k4UysktXb7bfbbtUt9Q@mail.gmail.com>
Date:   Thu, 8 Mar 2018 15:48:14 -0800
From:   Shakeel Butt <shakeelb@...gle.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Roman Gushchin <guro@...com>,
        Vladimir Davydov <vdavydov.dev@...il.com>,
        Michal Hocko <mhocko@...nel.org>,
        Greg Thelen <gthelen@...gle.com>,
        Johannes Weiner <hannes@...xchg.org>,
        Linux MM <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Cgroups <cgroups@...r.kernel.org>,
        David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH] mm: memcg: expose mem_cgroup_put API

On Thu, Mar 8, 2018 at 3:45 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Wed,  7 Mar 2018 18:48:50 -0800 Shakeel Butt <shakeelb@...gle.com> wrote:
>
>> This patch exports mem_cgroup_put API to put the refcnt of the memory
>> cgroup.
>
> OK, I remember now.  This is intended to make
> fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch independent of
> mm-oom-cgroup-aware-oom-killer.patch by extracting mem_cgroup_put()
> from mm-oom-cgroup-aware-oom-killer.patch.

Yes, you are right, it is needed by the above fsnotify patch.

> However it will not permit me to stage
> fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch ahead of
> mm-oom-cgroup-aware-oom-killer.patch because there are quite a lot of
> syntactic clashes.
>
> I can resolve those if needed, but am keenly hoping that the
> mm-oom-cgroup-aware-oom-killer.patch issues are resolved soon so there
> isn't a need to do this.
>

Sounds good to me.