netdev - Re: [PATCH v2 0/2] tg3: Fix handling of non-acceleration vlans

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:	Fri, 19 Sep 2014 17:39:46 -0700
From:	Prashant Sreedharan <prashant@...adcom.com>
To:	Vladislav Yasevich <vyasevich@...il.com>
CC:	<netdev@...r.kernel.org>, Vladislav Yasevich <vyasevic@...hat.com>,
	Michael Chan <mchan@...adcom.com>
Subject: Re: [PATCH v2 0/2] tg3:  Fix handling of non-acceleration vlans

On Fri, 2014-09-19 at 18:23 -0400, Vladislav Yasevich wrote:
> TG3 can't cope with checksum and TSO offloads when vlan headers were
> not accelerated.  This can be demonstrated with 802.1ad vlans or
> by configuring a vlan on top of a bridge and turning off vlan acceleration
> on the bridge device.
> 
> Instead of disabling all vlan acceleration, this series works around
> the issue by having tg3 driver call software segmentation and checksum
> generation.
> 
> v2: - moved the call to software segment soonner
>     - Preserve the checksum flags for TSO/LSO case and turn it off
>       if software checksum was computed.
>     - Add code to correctly receive full sized 802.1ad frames.
> 
> Vladislav Yasevich (2):
>   tg3: Work around HW/FW limitations with vlan encapsulated frames
>   tg3: Allow for receive of full-size 8021AD frames
> 
>  drivers/net/ethernet/broadcom/tg3.c | 21 ++++++++++++++++++++-
>  1 file changed, 20 insertions(+), 1 deletion(-)
> 
Acked-by: Prashant Sreedharan <prashant@...adcom.com>


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