Amend the bpf_redirect_peer() header documentation to also mention support for the netkit device type.
Showing the changes to include/uapi (1 of 1 file). Show all
Unified · Split
| @@ -4839,9 +4839,9 @@ union bpf_attr { · 4838 unmodified lines | |||
| 4839 | * going through the CPU's backlog queue. | 4839 | * going through the CPU's backlog queue. |
| 4840 | * | 4840 | * |
| 4841 | * The *flags* argument is reserved and must be 0. The helper is | 4841 | * The *flags* argument is reserved and must be 0. The helper is |
| 4842 | * currently only supported for tc BPF program types at the ingress | 4842 | * currently only supported for tc BPF program types at the |
| 4843 | * hook and for veth device types. The peer device must reside in a | 4843 | * ingress hook and for veth and netkit target device types. The |
| 4844 | * different network namespace. | 4844 | * peer device must reside in a different network namespace. |
| 4845 | * Return | 4845 | * Return |
| 4846 | * The helper returns **TC_ACT_REDIRECT** on success or | 4846 | * The helper returns **TC_ACT_REDIRECT** on success or |
| 4847 | * **TC_ACT_SHOT** on error. | 4847 | * **TC_ACT_SHOT** on error. |