netdev - Re: [PATCH v2 net-next 2/2] mm/vmpressure: add tracepoint for socket pressure detection

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: <ad52a9ca-bbbb-469f-8b8d-6a0f24ac3175@cdn77.com>
Date: Wed, 16 Jul 2025 10:47:42 +0200
From: Daniel Sedlak <daniel.sedlak@...77.com>
To: Kuniyuki Iwashima <kuniyu@...gle.com>
Cc: "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
 Jonathan Corbet <corbet@....net>, Neal Cardwell <ncardwell@...gle.com>,
 David Ahern <dsahern@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>,
 Shakeel Butt <shakeel.butt@...ux.dev>, Yosry Ahmed <yosry.ahmed@...ux.dev>,
 linux-mm@...ck.org, netdev@...r.kernel.org,
 Matyas Hurtik <matyas.hurtik@...77.com>,
 Daniel Sedlak <danie.sedlak@...77.com>
Subject: Re: [PATCH v2 net-next 2/2] mm/vmpressure: add tracepoint for socket
 pressure detection

Hi Kuniyuki,

On 7/15/25 7:46 PM, Kuniyuki Iwashima wrote:
>>>> Maybe a noob question: How can we translate the memcg ID
>>>> to the /sys/fs/cgroup/... path ?
>>>
>>> IMO this should be really named `cgroup_id` instead of `memcg_id`, but
>>> we kept the latter to keep consistency with the rest of the file.
>>>
>>> To find cgroup path you can use:
>>> - find /sys/fs/cgroup/ -inum `memcg_id`, and it will print "path" to the
>>> affected cgroup.
>>> - or you can use bpftrace tracepoint hooks and there is a helper
>>> function [1].
>>
>> Thanks, this is good to know and worth in the commit message.

Sure, I will add it to the v3.

>>>> It would be nice to place this patch first and the description of
>>>> patch 2 has how to use the new stat with this tracepoint.
>>>
>>> Sure, can do that. However, I am unsure how a good idea is to
>>> cross-reference commits, since each may go through a different tree
>>> because each commit is for a different subsystem. They would have to go
>>> through one tree, right?
>>
>> Right.
> 
> Sorry, I meant to say the two patches don't need to go along to a
> single tree and you can post them separately as each change is
> independent.

Just to make sure we are on the same page. Are you suggesting first 
posting this second patch to mm, and once (if) it gets merged, reference 
it from the first patch and send the first patch to netdev?

Thanks!
Daniel