From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check. Date: Fri, 2 Dec 2016 10:25:09 +0100 Message-ID: <20161202102509.065df1e8@griffin> References: <1480462253-114713-1-git-send-email-jarno@ovn.org> <1480462253-114713-2-git-send-email-jarno@ovn.org> <20161130145159.3cee7ba4@griffin> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Jarno Rajahalme , Linux Kernel Network Developers , Eric Garver To: Pravin Shelar Return-path: Received: from mx1.redhat.com ([209.132.183.28]:48702 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758611AbcLBJZN (ORCPT ); Fri, 2 Dec 2016 04:25:13 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 1 Dec 2016 11:50:00 -0800, Pravin Shelar wrote: > This is not changing any behavior compared to current OVS vlan checks. > Single vlan header is not considered for MTU check. It is changing it. Consider the case when there's an interface with MTU 1500 forwarding to an interface with MTU 1496. Obviously, full-sized vlan frames ingressing on the first interface are not forwardable to the second one. Yet, if the vlan tag is accelerated (and thus not counted in skb->len), is_skb_forwardable happily returns true because of the check len = dev->mtu + dev->hard_header_len + VLAN_HLEN; if (skb->len <= len) Jiri