From: Tejun Heo <htejun@fb.com>
To: Daniel Mack <daniel@zonque.org>
Cc: <daniel@iogearbox.net>, <ast@fb.com>, <davem@davemloft.net>,
<kafai@fb.com>, <fw@strlen.de>, <pablo@netfilter.org>,
<harald@redhat.com>, <netdev@vger.kernel.org>, <sargun@sargun.me>
Subject: Re: [PATCH v2 2/6] cgroup: add support for eBPF programs
Date: Wed, 24 Aug 2016 17:54:51 -0400 [thread overview]
Message-ID: <20160824215450.GA13455@htj.duckdns.org> (raw)
In-Reply-To: <1472070263-29988-3-git-send-email-daniel@zonque.org>
Hello, Daniel.
On Wed, Aug 24, 2016 at 10:24:19PM +0200, Daniel Mack wrote:
> +void cgroup_bpf_free(struct cgroup *cgrp)
> +{
> + unsigned int type;
> +
> + rcu_read_lock();
> +
> + for (type = 0; type < __MAX_BPF_ATTACH_TYPE; type++) {
> + if (!cgrp->bpf.prog[type])
> + continue;
> +
> + bpf_prog_put(cgrp->bpf.prog[type]);
> + static_branch_dec(&cgroup_bpf_enabled_key);
> + }
> +
> + rcu_read_unlock();
These rcu locking seem suspicious to me. RCU locking on writer side
is usually bogus. We sometimes do it to work around locking
assertions in accessors but it's a better idea to make the assertions
better in those cases - e.g. sth like assert_mylock_or_rcu_locked().
> +void cgroup_bpf_inherit(struct cgroup *cgrp, struct cgroup *parent)
> +{
> + unsigned int type;
> +
> + rcu_read_lock();
Ditto.
> + for (type = 0; type < __MAX_BPF_ATTACH_TYPE; type++)
> + rcu_assign_pointer(cgrp->bpf.prog_effective[type],
> + rcu_dereference(parent->bpf.prog_effective[type]));
> +
> + rcu_read_unlock();
> +}
...
> +void __cgroup_bpf_update(struct cgroup *cgrp,
> + struct cgroup *parent,
> + struct bpf_prog *prog,
> + enum bpf_attach_type type)
> +{
> + struct bpf_prog *old_prog, *effective;
> + struct cgroup_subsys_state *pos;
> +
> + rcu_read_lock();
Ditto.
> + old_prog = xchg(cgrp->bpf.prog + type, prog);
> + if (old_prog) {
> + bpf_prog_put(old_prog);
> + static_branch_dec(&cgroup_bpf_enabled_key);
> + }
> +
> + if (prog)
> + static_branch_inc(&cgroup_bpf_enabled_key);
Minor but probably better to inc first and then dec so that you can
avoid unnecessary enabled -> disabled -> enabled sequence.
> + effective = (!prog && parent) ?
> + rcu_dereference(parent->bpf.prog_effective[type]) : prog;
If this is what's triggering rcu warnings, there's an accessor to use
in these situations.
> + rcu_read_unlock();
> +
> + css_for_each_descendant_pre(pos, &cgrp->self) {
On the other hand, this walk actually requires rcu read locking unless
you're holding cgroup_mutex.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-08-24 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 20:24 [PATCH v2 0/6] Add eBPF hooks for cgroups Daniel Mack
2016-08-24 20:24 ` [PATCH v2 1/6] bpf: add new prog type for cgroup socket filtering Daniel Mack
2016-08-24 20:24 ` [PATCH v2 2/6] cgroup: add support for eBPF programs Daniel Mack
2016-08-24 21:54 ` Tejun Heo [this message]
2016-08-24 22:30 ` Daniel Mack
2016-08-25 6:56 ` kbuild test robot
2016-08-24 20:24 ` [PATCH v2 3/6] bpf: add BPF_PROG_ATTACH and BPF_PROG_DETACH commands Daniel Mack
2016-08-24 22:14 ` Tejun Heo
2016-08-24 20:24 ` [PATCH v2 4/6] net: filter: run cgroup eBPF ingress programs Daniel Mack
2016-08-24 20:24 ` [PATCH v2 5/6] net: core: run cgroup eBPF egress programs Daniel Mack
2016-08-24 20:24 ` [PATCH v2 6/6] samples: bpf: add userspace example for attaching eBPF programs to cgroups Daniel Mack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160824215450.GA13455@htj.duckdns.org \
--to=htejun@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=harald@redhat.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sargun@sargun.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).