netdev - Re: question regarding hw tx csum for IPv6

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1268768246.2091.32.camel@achroite.uk.solarflarecom.com>
Date:	Tue, 16 Mar 2010 19:37:26 +0000
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Blaschka <frank.blaschka@...ibm.com>
Cc:	netdev@...r.kernel.org
Subject: Re: question regarding hw tx csum for IPv6

On Tue, 2010-03-16 at 10:11 +0100, Blaschka wrote:
> Hi,
> 
> for me it looks like many network drivers exclude IPv6 frames from
> tx hw csum in case they have extended IPv6 headers. 
> Does the stack generates the csum for this kind of frames anyhow
> the device claims to do NETIF_F_HW_CSUM?

The NETIF_F_*_CSUM flags are for checksum generation, not checksum
validation.  The networking stack does not need to know about the
device's checksum validation capabilities but only needs to know whether
individual skbs have been validated.  If the device reports the
checksum(s) as invalid or if it cannot parse the packet you set
skb->ip_summed = CHECKSUM_NONE and it will be verified in software if
necessary.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
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