netdev - Re: [PATCH v10 bpf-next/net 3/6] net-memcg: Introduce net.core.memcg

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: <CAAVpQUBZSK6ptrRgruj0BGXBqDUOu3MKYKfD9FkWFn55OduwOw@mail.gmail.com>
Date: Mon, 22 Sep 2025 18:03:25 -0700
From: Kuniyuki Iwashima <kuniyu@...gle.com>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: Alexei Starovoitov <ast@...nel.org>, Andrii Nakryiko <andrii@...nel.org>, 
	Daniel Borkmann <daniel@...earbox.net>, Martin KaFai Lau <martin.lau@...ux.dev>, 
	John Fastabend <john.fastabend@...il.com>, Stanislav Fomichev <sdf@...ichev.me>, 
	Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>, 
	Roman Gushchin <roman.gushchin@...ux.dev>, "David S. Miller" <davem@...emloft.net>, 
	Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 
	Neal Cardwell <ncardwell@...gle.com>, Willem de Bruijn <willemb@...gle.com>, 
	Mina Almasry <almasrymina@...gle.com>, Kuniyuki Iwashima <kuni1840@...il.com>, bpf@...r.kernel.org, 
	netdev@...r.kernel.org
Subject: Re: [PATCH v10 bpf-next/net 3/6] net-memcg: Introduce
 net.core.memcg_exclusive sysctl.

On Mon, Sep 22, 2025 at 5:54 PM Shakeel Butt <shakeel.butt@...ux.dev> wrote:
>
> On Sat, Sep 20, 2025 at 12:07:17AM +0000, Kuniyuki Iwashima wrote:
> > diff --git a/net/core/sock.c b/net/core/sock.c
> > index 814966309b0e..348e599c3fbc 100644
> > --- a/net/core/sock.c
> > +++ b/net/core/sock.c
> > @@ -2519,6 +2519,7 @@ struct sock *sk_clone_lock(const struct sock *sk, const gfp_t priority)
> >  #ifdef CONFIG_MEMCG
> >       /* sk->sk_memcg will be populated at accept() time */
> >       newsk->sk_memcg = NULL;
> > +     mem_cgroup_sk_set_flags(newsk, mem_cgroup_sk_get_flags(sk));
>
> Why do you need to set the flag here? Will doing in __inet_accept only
> be too late i.e. protocol accounting would have happened?

Currently, we only allow bpf_setsockopt() during socket(2) not
to make things complicated as explained in patch 4.

So, this is to preserve the listener's flag set by bpf_setsockopt()
since network applications basically assume setsockopt() for a
listener socket is inherited to its child sockets.