netdev - Re: [PATCH] net: Take GSO into account when capturing packets

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

Date:	Mon, 06 Jul 2009 18:15:31 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	benjamin.poirier@...ymtl.ca
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	tcpdump-workers@...ts.tcpdump.org, wireshark-dev@...eshark.org
Subject: Re: [PATCH] net: Take GSO into account when capturing packets

From: Benjamin Poirier <benjamin.poirier@...ymtl.ca>
Date: Mon, 06 Jul 2009 14:04:32 -0400

> move the point where the support routine for packet capture is called to
> better reflect what is transmitted on the wire when GSO is active.
> 
> At the moment, packet capture (a la tcpdump) on the transmission side happens
> before GSO takes place (if it does). Therefore, even if a packet gets
> segmented by GSO, the capture shows that one big packet was sent when in fact
> many small packets were sent on the wire. This behavior does not reflect the
> "reality" of what is transmitted and could lead to confusion, especially since
> a capture on the receiving side shows the segmented packets.
> 
> Signed-off-by: Benjamin Poirier <benjamin.poirier@...ymtl.ca>

TSO does the same exact thing except that the networking card
chops up the packet before it hits the wire.

I really doubt there is anything seriously to gain by having
GSO behave one way and TSO another, and we should just keep
things as they are right now.

I'm not applying this, sorry.
--
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