[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200403133817.GW162390@mtj.duckdns.org>
Date: Fri, 3 Apr 2020 09:38:17 -0400
From: Tejun Heo <tj@...nel.org>
To: Dmitry Yakunin <zeil@...dex-team.ru>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
khlebnikov@...dex-team.ru, cgroups@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH v3 net] inet_diag: add cgroup id attribute
On Fri, Apr 03, 2020 at 12:56:27PM +0300, Dmitry Yakunin wrote:
> This patch adds cgroup v2 ID to common inet diag message attributes.
> Cgroup v2 ID is kernfs ID (ino or ino+gen). This attribute allows filter
> inet diag output by cgroup ID obtained by name_to_handle_at() syscall.
> When net_cls or net_prio cgroup is activated this ID is equal to 1 (root
> cgroup ID) for newly created sockets.
>
> Some notes about this ID:
>
> 1) gets initialized in socket() syscall
> 2) incoming socket gets ID from listening socket
> (not during accept() syscall)
How would this work with things like inetd? Would it make sense to associate the
socket on the first actual send/recv?
Thanks.
--
tejun
Powered by blists - more mailing lists