Re: [PATCH net-next v4 0/2] net: vrf: Fixup PKTINFO to return enslaved device index

From
David Miller <davem@davemloft.net>
Date
2016-05-11 23:33:14
Reply to
David Ahern, 2016-05-10
From: David Ahern <redacted>
Date: Tue, 10 May 2016 11:19:49 -0700
Applications such as OSPF and BFD need the original ingress device not
the VRF device; the latter can be derived from the former. To that end
move the packet intercept from an rx handler that is invoked by
__netif_receive_skb_core to the ipv4 and ipv6 receive processing.

IPv6 already saves the skb_iif to the control buffer in ipv6_rcv. Since
the skb->dev has not been switched the cb has the enslaved device. Make
the same happen for IPv4 by adding the skb_iif to inet_skb_parm and set
it in ipv4 code after clearing the skb control buffer similar to IPv6.
From there the pktinfo can just pull it from cb with the PKTINFO_SKB_CB
cast.
Series applied.
Thread (4 messages) 4 messages, 2 authors, last reply 2016-05-11
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help