netdev - question about UFO behavior for bridge device

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-next>] [day] [month] [year] [list]

Message-ID: <4DCCF803.5020805@cn.fujitsu.com>
Date:	Fri, 13 May 2011 17:21:07 +0800
From:	Shan Wei <shanwei@...fujitsu.com>
To:	单卫 <shanwei@...fujitsu.com>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Ben Hutchings <bhutchings@...arflare.com>,
	netdev <netdev@...r.kernel.org>
Subject: question about UFO behavior for bridge device

UDP protocol creates a big packet(skb) in which the data length is greater than MTU.

If device(eth0, lo) does not supports UFO, This big skb will be fragmented to
many fragments in IP protocol, and fragments are sent one by one by device.

But, if device(eth0, lo) supports UFO, IP protocol don't fragment it, and
device directly sends it out.

For bridge device which enable UFO, and Ethernet device(eth0) which not 
support UFO, IP protocol also doesn't fragment it, and bridge forwards original
skb to eth0. For this UFO disabled eth0, kernel needs to perform segmentation
on so big skb in dev_gso_segment(), and link segmented skbs to next field
of original skb. Then device sends segmented skbs out, but not original skb.

But, actually, i saw original big skb in eth0's tcpdump file, but not segmented skbs.
The behavior is right or what we want?
Is there anything missed about my analysis?

-- 
Best Regards
-----
Shan Wei
--
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