diff options
| author | Paolo Abeni <[email protected]> | 2018-07-30 14:30:42 +0200 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2018-07-30 09:31:13 -0700 |
| commit | 802bfb19152c0fb4137c6ba72bcf042ee023e743 (patch) | |
| tree | 0330695824cf2ca9a5f5d270e4a161f7df857abf /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | c87fffc57adf7b772b3778a9521c3f2ff744ae82 (diff) | |
net/sched: user-space can't set unknown tcfa_action values
Currently, when initializing an action, the user-space can specify
and use arbitrary values for the tcfa_action field. If the value
is unknown by the kernel, is implicitly threaded as TC_ACT_UNSPEC.
This change explicitly checks for unknown values at action creation
time, and explicitly convert them to TC_ACT_UNSPEC. No functional
changes are introduced, but this will allow introducing tcfa_action
values not exposed to user-space in a later patch.
Note: we can't use the above to hide TC_ACT_REDIRECT from user-space,
as the latter is already part of uAPI.
v3 -> v4:
- use an helper to check for action validity (JiriP)
- emit an extack for invalid actions (JiriP)
v4 -> v5:
- keep messages on a single line, drop net_warn (Marcelo)
Signed-off-by: Paolo Abeni <[email protected]>
Acked-by: Jiri Pirko <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions