netdev - Re: LRO/GSO interaction when packets are forwarded

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: <20080423.034225.176998769.davem@davemloft.net>
Date:	Wed, 23 Apr 2008 03:42:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jarkao2@...il.com
Cc:	bhutchings@...arflare.com, stephen.hemminger@...tta.com,
	kmansley@...arflare.com, shemminger@...tta.com,
	netdev@...r.kernel.org
Subject: Re: LRO/GSO interaction when packets are forwarded

From: Jarek Poplawski <jarkao2@...il.com>
Date: Wed, 23 Apr 2008 10:38:10 +0000

> Thanks for explanation! I'd still like to know why it's wrong, and
> why we should turn this off on a device with ip_forwarding enabled
> without checking how smart this hardware is?

It's not about how smart the hardware is.

This a stateless feature, the device accumulates data into
large receive frames when it's TCP and the ports and addresses
match.

There is no knowledge of routes or anything like that, nor should
there be, because otherwise it would cease to be stateless.
--
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