[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181203175525.GA31090@castle.DHCP.thefacebook.com>
Date: Mon, 3 Dec 2018 17:55:32 +0000
From: Roman Gushchin <guro@...com>
To: Tejun Heo <tj@...nel.org>
CC: Roman Gushchin <guroan@...il.com>, Oleg Nesterov <oleg@...hat.com>,
"Dan Carpenter" <dan.carpenter@...cle.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH v4 3/7] cgroup: protect cgroup->nr_(dying_)descendants by
css_set_lock
On Mon, Dec 03, 2018 at 08:17:06AM -0800, Tejun Heo wrote:
> On Fri, Nov 30, 2018 at 03:47:41PM -0800, Roman Gushchin wrote:
> > + * nr_descendants and nr_dying_descendants are protected
> > + * by cgroup_mutex and css_set_lock.
>
> Can you be a bit more specific - hold both for writes, either for
> reads.
Sure. Thanks!
Powered by blists - more mailing lists