summaryrefslogtreecommitdiff
path: root/include/net
diff options
context:
space:
mode:
authorShmulik Ladkani <sladkani@proofpoint.com>2019-12-25 10:51:01 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-01-04 19:18:45 +0100
commit1f754ad07751771b4e85f2e821d5a0618a6b861d (patch)
tree4df105e00a31ba29decb87acf3436f1e8c66338e /include/net
parentfbeec8f00b01644d094bf883b963fb6790b02666 (diff)
net/sched: act_mirred: Pull mac prior redir to non mac_header_xmit device
[ Upstream commit 70cf3dc7313207816255b9acb0dffb19dae78144 ] There's no skb_pull performed when a mirred action is set at egress of a mac device, with a target device/action that expects skb->data to point at the network header. As a result, either the target device is errornously given an skb with data pointing to the mac (egress case), or the net stack receives the skb with data pointing to the mac (ingress case). E.g: # tc qdisc add dev eth9 root handle 1: prio # tc filter add dev eth9 parent 1: prio 9 protocol ip handle 9 basic \ action mirred egress redirect dev tun0 (tun0 is a tun device. result: tun0 errornously gets the eth header instead of the iph) Revise the push/pull logic of tcf_mirred_act() to not rely on the skb_at_tc_ingress() vs tcf_mirred_act_wants_ingress() comparison, as it does not cover all "pull" cases. Instead, calculate whether the required action on the target device requires the data to point at the network header, and compare this to whether skb->data points to network header - and make the push/pull adjustments as necessary. Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") Signed-off-by: Shmulik Ladkani <sladkani@proofpoint.com> Tested-by: Jamal Hadi Salim <jhs@mojatatu.com> Acked-by: Jamal Hadi Salim <jhs@mojatatu.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions