[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOviyai2LMkFJuOhc=ZEckuackTnfPBwCsB6aLxTBJD3-vb1=w@mail.gmail.com>
Date: Tue, 9 Jun 2015 17:20:58 +1000
From: Aleksa Sarai <cyphar@...har.com>
To: Tejun Heo <tj@...nel.org>
Cc: lizefan@...wei.com, mingo@...hat.com,
Peter Zijlstra <peterz@...radead.org>, richard@....at,
Frédéric Weisbecker <fweisbec@...il.com>,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org
Subject: Re: [PATCH v13 4/5] cgroup: allow a cgroup subsystem to reject a fork
>> @@ -4924,6 +4927,7 @@ static void __init cgroup_init_subsys(struct cgroup_subsys *ss, bool early)
>>
>> have_fork_callback |= (bool)ss->fork << ss->id;
>> have_exit_callback |= (bool)ss->exit << ss->id;
>> + have_canfork_callback |= (bool)ss->can_fork << ss->id;
>
> Hmmm.... do we still need this mask? We're already restricting
> iteration pretty heavily.
CGROUP_CANFORK_{START,END,COUNT} aren't used to restrict the
iteration. They're used for restricting the size of the @ss_priv
array. If you want, I can use CANFORK_{START,END} to restrict the
iteration -- I just prefer using the for_each_subsys_which API for
iterating over active cgroups. :/
--
Aleksa Sarai (cyphar)
www.cyphar.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists