From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH RFC net-next 00/11] udp gso Date: Wed, 18 Apr 2018 15:33:18 -0400 (EDT) Message-ID: <20180418.153318.51295736872496660.davem@davemloft.net> References: <20180418123103.GC19633@oracle.com> <20180418.132808.1710130437020293308.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: sowmini.varadhan@oracle.com, willemdebruijn.kernel@gmail.com, sridhar.samudrala@intel.com, netdev@vger.kernel.org, willemb@google.com To: alexander.duyck@gmail.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:47388 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750824AbeDRTdW (ORCPT ); Wed, 18 Apr 2018 15:33:22 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Alexander Duyck Date: Wed, 18 Apr 2018 11:12:06 -0700 > My only concern with the patch set is verifying what mitigations are > in case so that we aren't trying to set an MSS size that results in a > frame larger than MTU. I'm still digging through the code and trying > to grok it, but I figured I might just put the question out there to > may my reviewing easier. It signals an error if a too large segment size is requested.