[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220810170706.ikyrsuzupjwt65h7@google.com>
Date: Wed, 10 Aug 2022 17:07:06 +0000
From: Shakeel Butt <shakeelb@...gle.com>
To: Yafang Shao <laoar.shao@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
haoluo@...gle.com, jolsa@...nel.org, hannes@...xchg.org,
mhocko@...nel.org, roman.gushchin@...ux.dev,
songmuchun@...edance.com, akpm@...ux-foundation.org,
netdev@...r.kernel.org, bpf@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH bpf-next 05/15] bpf: Fix incorrect mem_cgroup_put
On Wed, Aug 10, 2022 at 03:18:30PM +0000, Yafang Shao wrote:
> The memcg may be the root_mem_cgroup, in which case we shouldn't put it.
No, it is ok to put root_mem_cgroup. css_put already handles the root
cgroups.
Powered by blists - more mailing lists