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
| ||
|
Date: Tue, 30 Sep 2014 12:22:57 -0700 From: Eric Dumazet <eric.dumazet@...il.com> To: Yuval Mintz <Yuval.Mintz@...gic.com> Cc: "Tom Herbert (Partner - google)" <therbert@...gle.com>, netdev <netdev@...r.kernel.org> Subject: RE: How exactly does CHECKSUM_COMPLETE works? On Tue, 2014-09-30 at 19:05 +0000, Yuval Mintz wrote: > Can you pinpoint me to what exactly in the code corrects NAPI_GRO_CB(skb)->csum > by negating the ipv4 part in the ones' complete checksum? > > E.g., for ipv6 [in ipv6_gro_receive()] I can see that skb_gro_postpull_rcsum() is > called after pulling the ipv6 header [and before proceeding to the next protocol], > but I can't seem to find anything similar to this for ipv4 [in inet_gro_receive()]. > IPv4 header is supposed to have a 0 checksum ;) -- 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