cls_bpf: further limit exec opcodes subset
authorDaniel Borkmann <daniel@iogearbox.net>
Wed, 23 Sep 2015 19:56:48 +0000 (21:56 +0200)
committerDavid S. Miller <davem@davemloft.net>
Wed, 23 Sep 2015 21:29:02 +0000 (14:29 -0700)
commit5cf8ca0e473df01c9b78894d6e62afa2e1d1166f
tree65ef1d74e2df607b83bfb534a121342488d22a49
parentef146fa40cc3af1dcb13688f41cc06a9c0deb01c
cls_bpf: further limit exec opcodes subset

Jamal suggested to further limit the currently allowed subset of opcodes
that may be used by a direct action return code as the intention is not
to replace the full action engine, but rather to have a minimal set that
can be used in the fast-path on things like ingress for some features
that cls_bpf supports.

Classifiers can, of course, still be chained together that have direct
action mode with those that have a full exec pass. For more complex
scenarios that go beyond this minimal set here, the full tcf_exts_exec()
path must be used.

Suggested-by: Jamal Hadi Salim <jhs@mojatatu.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/sched/cls_bpf.c