From: Martin KaFai Lau <kafai-b10kYP2dOMg@public.gmane.org>
To: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Alexei Starovoitov <ast-b10kYP2dOMg@public.gmane.org>,
Daniel Borkmann <daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
kernel-team-b10kYP2dOMg@public.gmane.org
Subject: [PATCH -next 0/4] cgroup: bpf: cgroup2 membership test on skb
Date: Tue, 21 Jun 2016 17:23:18 -0700 [thread overview]
Message-ID: <1466555002-1316296-1-git-send-email-kafai@fb.com> (raw)
This series is to implement a bpf-way to
check the cgroup2 membership of a skb (sk_buff).
It is similar to the feature added in netfilter:
c38c4597e4bf ("netfilter: implement xt_cgroup cgroup2 path match")
The current target is the tc-like usage.
next reply other threads:[~2016-06-22 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 0:23 Martin KaFai Lau [this message]
2016-06-22 0:23 ` [PATCH -next 2/4] cgroup: bpf: Add BPF_MAP_TYPE_CGROUP_ARRAY Martin KaFai Lau
2016-06-22 1:15 ` Alexei Starovoitov
[not found] ` <1466555002-1316296-3-git-send-email-kafai-b10kYP2dOMg@public.gmane.org>
2016-06-22 2:33 ` kbuild test robot
[not found] ` <1466555002-1316296-1-git-send-email-kafai-b10kYP2dOMg@public.gmane.org>
2016-06-22 0:23 ` [PATCH -next 1/4] cgroup: Add cgroup_get_from_fd Martin KaFai Lau
2016-06-22 15:35 ` Tejun Heo
2016-06-22 0:23 ` [PATCH -next 3/4] cgroup: bpf: Add bpf_skb_in_cgroup_proto Martin KaFai Lau
2016-06-22 1:15 ` Alexei Starovoitov
2016-06-22 6:19 ` Martin KaFai Lau
[not found] ` <1466555002-1316296-4-git-send-email-kafai-b10kYP2dOMg@public.gmane.org>
2016-06-22 1:25 ` kbuild test robot
2016-06-22 2:15 ` kbuild test robot
2016-06-22 0:23 ` [PATCH -next 4/4] cgroup: bpf: Add an example to do cgroup checking in BPF Martin KaFai Lau
[not found] ` <1466555002-1316296-5-git-send-email-kafai-b10kYP2dOMg@public.gmane.org>
2016-06-22 1:19 ` Alexei Starovoitov
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=1466555002-1316296-1-git-send-email-kafai@fb.com \
--to=kafai-b10kyp2domg@public.gmane.org \
--cc=ast-b10kYP2dOMg@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org \
--cc=kernel-team-b10kYP2dOMg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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