d68cb48e90
We want to label /sys/fs/bpf/tethering/... with a new label distinct from /sys/fs/bpf, as this will allow locking down the programs/maps tighter then is currently possible with the existing system. These programs and maps are provided via the tethering mainline module, and as such their number, names, key/value types, etc. are all prone to be changed by a tethering mainline module update. Test: atest, TreeHugger Signed-off-by: Maciej Żenczykowski <maze@google.com> Change-Id: Ifc4108d76a1106a936b941a3dda1abc5a65c05b0 |
||
---|---|---|
.. | ||
26.0 | ||
27.0 | ||
28.0 | ||
29.0 | ||
30.0 |