linux-kernel - Re: [PATCH nft] nft: memcg accounting for dynamically allocated objects

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: <20220401230158.GC28321@breakpoint.cc>
Date:   Sat, 2 Apr 2022 01:01:58 +0200
From:   Florian Westphal <fw@...len.de>
To:     Roman Gushchin <roman.gushchin@...ux.dev>
Cc:     Florian Westphal <fw@...len.de>,
        Vasily Averin <vasily.averin@...ux.dev>,
        Pablo Neira Ayuso <pablo@...filter.org>, kernel@...nvz.org,
        Jozsef Kadlecsik <kadlec@...filter.org>,
        netfilter-devel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH nft] nft: memcg accounting for dynamically allocated
 objects

Roman Gushchin <roman.gushchin@...ux.dev> wrote:
> On Fri, Apr 01, 2022 at 09:31:59PM +0200, Florian Westphal wrote:
> > But what task/memcg is used for the accounting in that case?
> 
> Root memcg/no accounting, which is the same.
> 
> There is a way to account for a specific memcg in such cases, it's used for
> bpf maps, for example. We save a pointer to the memcg which created the map and
> charge it for all allocations from a !in_task context.

Great, so we could use same scheme later on if its required for some
use case.

>  so let's not do without regression tests and a serious need.

Sounds good. Thanks.