netdev - Re: csum offload and af

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]

Date:	Tue, 12 Aug 2008 17:55:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	netdev@...eo.de, rusty@...tcorp.com.au, anthony@...emonkey.ws,
	netdev@...r.kernel.org
Subject: Re: csum offload and af_packet

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Wed, 13 Aug 2008 09:37:53 +1000

> Oh I totally agree that there are lots of scenarios where you
> want to have an unmolested guest image.  My point was that if
> you're going to touch the guest kernel anyway you might as well
> fix the guest user-space instead.
> 
> This is also why I've argued that the default should be to disable
> TX checksums until the guest enables it so that old guests that
> know nothing about this can continue to work.

However, I think Rusty may have a point.

The whole point of the auxdata thing was that if your tool is smart
you can get the notification that the checksum is going to be HW
computed and therefore keep capturing at a very low cost.

But for a stupid AF_PACKET user, like dhclient currently is, there is
no harm in COW'ing the packet header area and calculating the checksum
for them in this case.

I kind of hope that libpcap/tcpdump has been taught about auxdata
by now, has it? :-/

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