[PATCHSET v3] netfilter, cgroup: implement cgroup2 path match in xt_cgroup
From: Tejun Heo
Date: Sat Nov 21 2015 - 11:15:12 EST
This is v3 of the xt_cgroup2 patchset. Changes from the last take are
* Folded cgroup2 path matching into xt_cgroup as a new revision rather
than a separate xt_cgroup2 match as suggested by Pablo.
* Refreshed on top of Nina's net_cls dynamic config update fix patch.
I included the fix patch as part of this series to ease reviewing.
The changes from v1 to v2 are
* Instead of adding sock->sk_cgroup separately, sock->sk_cgrp_data now
carries either (prioidx, classid) pair or cgroup2 pointer. This
avoids inflating struct sock with yet another cgroup related field.
Unfortunately, this does add some complexity but that's the
trade-off and the complexity is contained in cgroup proper.
* Various small updats as per David and Jan's reviews.
In cgroup v1, dealing with cgroup membership was difficult because the
number of membership associations was unbound. As a result, cgroup v1
grew several controllers whose primary purpose is either tagging
membership or pull in configuration knobs from other subsystems so
that cgroup membership test can be avoided.
net_cls and net_prio controllers are examples of the latter. They
allow configuring network-specific attributes from cgroup side so that
network subsystem can avoid testing cgroup membership; unfortunately,
these are not only cumbersome but also problematic.
Both net_cls and net_prio aren't properly hierarchical. Both inherit
configuration from the parent on creation but there's no interaction
afterwards. An ancestor doesn't restrict the behavior in its subtree
in anyway and configuration changes aren't propagated downwards.
Especially when combined with cgroup delegation, this is problematic
because delegatees can mess up whatever network configuration
implemented at the system level. net_prio would allow the delegatees
to set whatever priority value regardless of CAP_NET_ADMIN and net_cls
the same for classid.
While it is possible to solve these issues from controller side by
implementing hierarchical allowable ranges in both controllers, it
would involve quite a bit of complexity in the controllers and further
obfuscate network configuration as it becomes even more difficult to
tell what's actually being configured looking from the network side.
While not much can be done for v1 at this point, as membership
handling is sane on cgroup v2, it'd be better to make cgroup matching
behave like other network matches and classifiers than introducing
This patchset includes the following nine patches.
0001-0003 are prepatory patches in kernfs and cgroup. These patches
are available in the following branch which will stay stable.
0004 is the following net_cls config update fix patch included in this
series to ease reviewing as it causes a conflict with a later patch in
0005-0007 consolidate two cgroup related fields in struct sock into
cgroup_sock_data and update it so that it can alternatively carry a
0008-0009 implement cgroup2 patch matching in xt_cgroup.
This patchset is on top of v4.4-rc1 and also available in the
following git branch.
I'll post iptables extension as a reply. diffstat follows. Thanks.
fs/kernfs/dir.c | 46 +++++++++++
include/linux/cgroup-defs.h | 126 +++++++++++++++++++++++++++++++
include/linux/cgroup.h | 66 +++++++++++++++-
include/linux/kernfs.h | 12 ++
include/net/cls_cgroup.h | 11 +-
include/net/netprio_cgroup.h | 16 +++
include/net/sock.h | 13 ---
include/uapi/linux/netfilter/xt_cgroup.h | 15 +++
kernel/cgroup.c | 126 ++++++++++++++++++++++++-------
net/Kconfig | 6 +
net/core/dev.c | 3
net/core/netclassid_cgroup.c | 37 ++++++---
net/core/netprio_cgroup.c | 19 ++++
net/core/scm.c | 4
net/core/sock.c | 17 ----
net/netfilter/nft_meta.c | 2
net/netfilter/xt_cgroup.c | 108 ++++++++++++++++++++++----
17 files changed, 531 insertions(+), 96 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/