From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shmulik Ladkani Subject: Re: [RFC PATCH] net: ip_finish_output_gso: Attempt gso_size clamping if segments exceed mtu Date: Mon, 22 Aug 2016 16:05:34 +0300 Message-ID: <20160822160534.6b2afd8f@pixies> References: <1471867570-1406-1-git-send-email-shmulik.ladkani@gmail.com> <20160822125842.GF6199@breakpoint.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , netdev@vger.kernel.org, Hannes Frederic Sowa , Eric Dumazet To: Florian Westphal Return-path: Received: from mail-wm0-f65.google.com ([74.125.82.65]:36198 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752538AbcHVNFo (ORCPT ); Mon, 22 Aug 2016 09:05:44 -0400 Received: by mail-wm0-f65.google.com with SMTP id i138so13360121wmf.3 for ; Mon, 22 Aug 2016 06:05:43 -0700 (PDT) In-Reply-To: <20160822125842.GF6199@breakpoint.cc> Sender: netdev-owner@vger.kernel.org List-ID: Hi, On Mon, 22 Aug 2016 14:58:42 +0200, fw@strlen.de wrote: > > > > Florian, in fe6cc55f you described a BUG due to gso_size decrease. > > I've tested both bridged and routed cases, but in my setups failed to > > hit the issue; Appreciate if you can provide some hints. > > Still get the BUG, I applied this patch on top of net-next. > > On hypervisor: > 10.0.0.2 via 192.168.7.10 dev tap0 mtu lock 1500 > ssh root@10.0.0.2 'cat > /dev/null' < /dev/zero > > On vm1 (which dies instantly, see below): > eth0 mtu 1500 (192.168.7.10) > eth1 mtu 1280 (10.0.0.1) > > On vm2 > eth0 mtu 1280 (10.0.0.2) > > Normal ipv4 routing via vm1, no iptables etc. present, so > > we have hypervisor 1500 -> 1500 VM1 1280 -> 1280 VM2 > > Turning off gro avoids this problem. Thanks Florian, will dive into this.