netdev - Re: [PATCH] af_packet: account for VLAN when checking packet size

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]

Message-Id: <20101027.084854.71130929.davem@davemloft.net>
Date:	Wed, 27 Oct 2010 08:48:54 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	horms@...ge.net.au
Cc:	mst@...hat.com, eric.dumazet@...il.com, netdev@...r.kernel.org,
	johann.baudy@...-log.net
Subject: Re: [PATCH] af_packet: account for VLAN when checking packet size

From: Simon Horman <horms@...ge.net.au>
Date: Fri, 22 Oct 2010 10:41:26 +0200

> Incidently, I believe that this problem will only become more acute
> and complex if support for 802.1ad (Provider Bridges, aka Q-in-Q),
> 802.1ah (Provider Backbone Bridges, aka MAC-in-MAC) or other standards
> which further extend the maximum frame size.

No doubt.

> Dave, you were mentioning to me the other day that the kernel
> already supports some notion of Q-in-Q (though its not 802.1ad).
> Does the current implementation allow for frames > 1504 bytes?

It's only going to hardware offload and allow the extra space
for the outer-most VLAN tag.  Everthing inside of the outer
tag will be handled in software as far as Linux is concerned.

> Is that a complication to the change proposed here?

For now, I don't think so.
--
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