lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <alpine.LFD.2.11.1605052248480.2328@ja.home.ssi.bg> Date: Thu, 5 May 2016 23:00:36 +0300 (EEST) From: Julian Anastasov <ja@....bg> To: David Ahern <dsa@...ulusnetworks.com> cc: netdev@...r.kernel.org Subject: Re: [PATCH net-next 06/13] net: original ingress device index in PKTINFO 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 spend cycles in fast path in case nobody > > listens for such info. > > Why is that? skb_iif is set to skb->dev->index in __netif_receive_skb_core and > ip_rcv is called it. Is there another path to it? You are right, it is 0 only for the output path. Regards -- Julian Anastasov <ja@....bg>
Powered by blists - more mailing lists