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: <20120206.120015.1104308784569339801.davem@davemloft.net> Date: Mon, 06 Feb 2012 12:00:15 -0500 (EST) From: David Miller <davem@...emloft.net> To: ogerlitz@...lanox.com Cc: eric.dumazet@...il.com, sean.hefty@...el.com, herbert@...dor.hengli.com.au, linux-rdma@...r.kernel.org, shlomop@...lanox.com, roland@...nel.org, netdev@...r.kernel.org Subject: Re: [PATCH net-next] gro: introduce gro_mac_header_len From: Or Gerlitz <ogerlitz@...lanox.com> Date: Mon, 6 Feb 2012 18:44:03 +0200 > As I wrote earlier on this thread, the reason is that in order to be > able to xmit skb's for which the stack doesn't provide a neighbour, > IPoIB makes sure to have extra INFINIBAND_ALEN bytes headroom on > skbs. Such that the ipoib hard_header functions writes a > "ipoib_pseudoheader" (= hw address) on the skb and the xmit function > grabs it from there and use that pseudoheader to search for the actual > IB L2 address handle kept for that dest. Example such skbs are unicast > ARP replies and multicast. see below some relevant code sections from > ipoib_main.c Then IPoIB is broken and must be fixed, see my other reply. We're not adding a bogus member to the netdevice just because IPoIB tries to do path resolution and neighbour validation behind the neighbour cache's back. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists