From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754323AbdCFOBN (ORCPT ); Mon, 6 Mar 2017 09:01:13 -0500 Received: from mail-wr0-f195.google.com ([209.85.128.195]:33582 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754243AbdCFOA6 (ORCPT ); Mon, 6 Mar 2017 09:00:58 -0500 Date: Mon, 6 Mar 2017 14:54:36 +0100 From: Jiri Pirko To: Jarod Wilson Cc: linux-kernel@vger.kernel.org, Cong Wang , netdev@vger.kernel.org Subject: Re: [PATCH net] team: use ETH_MAX_MTU as max mtu Message-ID: <20170306135436.GD1822@nanopsycho.orion> References: <20170306134858.2096-1-jarod@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170306134858.2096-1-jarod@redhat.com> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mon, Mar 06, 2017 at 02:48:58PM CET, jarod@redhat.com wrote: >This restores the ability to set a team device's mtu to anything higher >than 1500. Similar to the reported issue with bonding, the team driver >calls ether_setup(), which sets an initial max_mtu of 1500, while the >underlying hardware can handle something much larger. Just set it to >ETH_MAX_MTU to support all possible values, and the limitations of the >underlying devices will prevent setting anything too large. > >Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra") >CC: Cong Wang >CC: Jiri Pirko >CC: netdev@vger.kernel.org >Signed-off-by: Jarod Wilson Acked-by: Jiri Pirko