Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-12-09 Thread Jiri Benc
On Thu, 8 Dec 2016 15:50:41 -0500, Eric Garver wrote: > Should we not also follow the "skbs are untagged" approach that the rest > of the kernel uses? I'm referring to patches 1 and 2 form Jiri's series > "openvswitch: make vlan handling consistent". > > With those changes is_skb_forwardable() wou

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-12-08 Thread Eric Garver
On Sun, Dec 04, 2016 at 04:22:40PM -0800, Pravin Shelar wrote: > On Fri, Dec 2, 2016 at 1:25 AM, Jiri Benc wrote: > > 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 MT

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-12-04 Thread Pravin Shelar
On Fri, Dec 2, 2016 at 1:25 AM, Jiri Benc wrote: > 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 i

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-12-02 Thread Jiri Benc
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 1

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-12-01 Thread Pravin Shelar
On Wed, Nov 30, 2016 at 5:51 AM, Jiri Benc wrote: > On Tue, 29 Nov 2016 15:30:52 -0800, Jarno Rajahalme wrote: >> @@ -504,11 +485,20 @@ void ovs_vport_send(struct vport *vport, struct >> sk_buff *skb, u8 mac_proto) >> goto drop; >> } >> >> - if (unlikely(packet_length(skb,

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-11-30 Thread Jarno Rajahalme
> On Nov 30, 2016, at 5:51 AM, Jiri Benc wrote: > > On Tue, 29 Nov 2016 15:30:52 -0800, Jarno Rajahalme wrote: >> @@ -504,11 +485,20 @@ void ovs_vport_send(struct vport *vport, struct >> sk_buff *skb, u8 mac_proto) >> goto drop; >> } >> >> -if (unlikely(packet_length(skb,

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-11-30 Thread Jiri Benc
On Tue, 29 Nov 2016 15:30:52 -0800, Jarno Rajahalme wrote: > @@ -504,11 +485,20 @@ void ovs_vport_send(struct vport *vport, struct sk_buff > *skb, u8 mac_proto) > goto drop; > } > > - if (unlikely(packet_length(skb, vport->dev) > mtu && > - !skb_is_gso(sk

Re: [PATCH v3 net-next 2/3] openvswitch: Use is_skb_forwardable() for length check.

2016-11-29 Thread Pravin Shelar
On Tue, Nov 29, 2016 at 3:30 PM, Jarno Rajahalme wrote: > Use is_skb_forwardable() instead of an explicit length check. This > gets around the apparent MTU check failure in OVS test cases when > skb->protocol is not properly set in case of non-accelerated VLAN > skbs. > > Suggested-by: Pravin She