linux-kernel - Re: Re: [PATCH] mm/vmstats: add counters for the page frag cache

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <bdd6088e-0318-a90a-1e22-e7d668c7aec4@lge.com>
Date:   Mon, 4 Sep 2017 10:36:42 +0900
From:   Kyeongdon Kim <kyeongdon.kim@....com>
To:     Michal Hocko <mhocko@...nel.org>,
        Konstantin Khlebnikov <khlebnikov@...dex-team.ru>
Cc:     akpm@...ux-foundation.org, sfr@...b.auug.org.au,
        ying.huang@...el.com, vbabka@...e.cz, hannes@...xchg.org,
        xieyisheng1@...wei.com, luto@...nel.org, shli@...com,
        mgorman@...hsingularity.net, hillf.zj@...baba-inc.com,
        kemi.wang@...el.com, rientjes@...gle.com, bigeasy@...utronix.de,
        iamjoonsoo.kim@....com, bongkyu.kim@....com,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: Re: [PATCH] mm/vmstats: add counters for the page frag cache

Thanks for your reply,

We already used other i/f like page_owner and kmemleak to resolve memory 
leakage issue.
But, page_owner can only for guess but cannot find intuitively memory 
usage regarding page_frag_cache.
And kmemleak cannot use (because of calling directly 
__alloc_pages_nodemask()).

Additionally, some embedded linux like Android or something..
is not able to always use kmemleak & page_owner because of runtime 
performance deterioration.
However, the root cause of this memory issue is from net device like 
wireless.
In short, should always use wireless on device but, cannot use those 
memory debug tools.

That's why those counters need..
and for much cheaper I can remove pgfrag_alloc_calls and pgfrag_free_calls.

Thanks,
Kyeongdon Kim

On 2017-09-01 오후 6:21, Michal Hocko wrote:
> On Fri 01-09-17 12:12:36, Konstantin Khlebnikov wrote:
> > IMHO that's too much counters.
> > Per-node NR_FRAGMENT_PAGES should be enough for guessing what's 
> going on.
> > Perf probes provides enough features for furhter debugging.
>
> I would tend to agree. Adding a counter based on a single debugging
> instance sounds like an overkill to me. Counters should be pretty cheep
> but this is way too specialized API to export to the userspace.
>
> We have other interfaces to debug memory leaks like page_owner.
> -- 
> Michal Hocko
> SUSE Labs