Re: [PATCH net-next 06/13] net: original ingress device index in PKTINFO

2016-05-05 Thread Julian Anastasov
Hello, On Thu, 5 May 2016, David Ahern wrote: > On 5/5/16 2:41 AM, Julian Anastasov wrote: > > > + IPCB(skb)->iif = skb->skb_iif; > > > > For loopback traffic (including looped back multicast) > > this is now a zero :( Can inet_iif be moved to ip_rcv_finish > > instead? Still, we sp

Re: [PATCH net-next 06/13] net: original ingress device index in PKTINFO

2016-05-05 Thread David Ahern
On 5/5/16 2:41 AM, Julian Anastasov wrote: Hello, On Wed, 4 May 2016, David Ahern wrote: 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 add the skb_iif to inet_skb_parm and set it in ipv4 co

Re: [PATCH net-next 06/13] net: original ingress device index in PKTINFO

2016-05-05 Thread Julian Anastasov
Hello, On Wed, 4 May 2016, David Ahern wrote: > 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 > add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing > the skb control buff

[PATCH net-next 06/13] net: original ingress device index in PKTINFO

2016-05-04 Thread David Ahern
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 add 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