Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2203901imm; Mon, 28 May 2018 03:53:51 -0700 (PDT) X-Google-Smtp-Source: AB8JxZppPVfJ1X81L+SwN0i8DdVR3SV3JYh5GbT8dYYRM5Q3baFxIvKRuStGu/bfWA0wTYj9zbX5 X-Received: by 2002:a62:4651:: with SMTP id t78-v6mr13038233pfa.46.1527504831029; Mon, 28 May 2018 03:53:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527504831; cv=none; d=google.com; s=arc-20160816; b=AlKpiiydPEblIjk/4JaU1bz3oITSElOF3T+UtQfnskrpmawPk4UXXdq21kkxfGfBaG gVvjUAxbOo9YQ1+Knb/uRGaGs31TJHuYKwYN2gbFNn/EHGBSfa6iiMVT+z8VeI2WRZvO GC4dakXZJMhRrA3PWe0z8nk42Oh1TDBJHFlpTj7f6ERGO3aikkwvWbiuXuaVT8PWdOin 1BjBRwWSqHyM+VHsc7ySU2DM4OC/F1hRLah8tW2FWWdUmBb6AWsOikcK9MPNwKOUynby KokpJdTv5hODs4DAX3R10sjL+cvftUe54uwhRW4C+QF63XZBd4rUSKf14SeCoXfuSYL5 1PXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=W9GHFm4MS2j4JIewT5fEK6VPJKekRV7bTFklXB7UczA=; b=tlGzKpd2WHj/eTzB9faMO2u+cyBgLBUY0N6+VM7OhjrtIqIdgUA/ZludTXySJM1AkP GbqqQeRPZzMrRUSx5+bBekW4d4IRQd+nIPvH5s1afgFtvnZyUyeuPl70yhIqYV4cD8hg cCN12NF5XBv5vaUXV3sYS5C3i3FRGRMXtu38MRKeycSLy3Quz/DIl9iUpX681H5MOw/R YC6NxEwhzf7oCuK9pWD853iIds7MPMQ5eUE7eyAZg3HVStawLbU9w+xTQhmBmfe+aGzx 76RvRsemVXqpieXA1TUvNmc0W+TdRQfJDGrBsAH8b/2JxTP4DeRqMu4PZC6Z6TdhBYZp jZZQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=bNwFegto; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j5-v6si23988943pgt.449.2018.05.28.03.53.36; Mon, 28 May 2018 03:53:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=bNwFegto; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1164121AbeE1KxV (ORCPT + 99 others); Mon, 28 May 2018 06:53:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:42472 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1163629AbeE1KxP (ORCPT ); Mon, 28 May 2018 06:53:15 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2CEB6204EE; Mon, 28 May 2018 10:53:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527504794; bh=D+ivAlbmN/XLEt1+ig6XYDQ90Dne4QoFOTZOQLq9f1E=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=bNwFegtopYnLdG6JO96bl2AHywI2P5rbZSYU7WbNo2h/03VkzqHvs3JMJ+MZzbouX 0Qt9M9N9a1W5RLDT8y/acz2m6BU/mCMTkTVAfbvcR5ghT8E10u7oLP6UAXWm1K5SFv C5hjDe3JagY7XgrbRmK4EDDnR/BTMzdwIMSZQIfI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Stefano Brivio , Sabrina Dubroca , Steffen Klassert , Sasha Levin Subject: [PATCH 4.14 266/496] vti6: Fix dev->max_mtu setting Date: Mon, 28 May 2018 12:00:51 +0200 Message-Id: <20180528100331.071260733@linuxfoundation.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180528100319.498712256@linuxfoundation.org> References: <20180528100319.498712256@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Stefano Brivio [ Upstream commit f8a554b4aa9686bb2c12f6bae516e58783289a03 ] We shouldn't allow a tunnel to have IP_MAX_MTU as MTU, because another IPv6 header is going on top of our packets. Without this patch, we might end up building packets bigger than IP_MAX_MTU. Fixes: b96f9afee4eb ("ipv4/6: use core net MTU range checking") Signed-off-by: Stefano Brivio Acked-by: Sabrina Dubroca Signed-off-by: Steffen Klassert Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- net/ipv6/ip6_vti.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/net/ipv6/ip6_vti.c +++ b/net/ipv6/ip6_vti.c @@ -852,7 +852,7 @@ static void vti6_dev_setup(struct net_de dev->hard_header_len = LL_MAX_HEADER + sizeof(struct ipv6hdr); dev->mtu = ETH_DATA_LEN; dev->min_mtu = IPV6_MIN_MTU; - dev->max_mtu = IP_MAX_MTU; + dev->max_mtu = IP_MAX_MTU - sizeof(struct ipv6hdr); dev->flags |= IFF_NOARP; dev->addr_len = sizeof(struct in6_addr); netif_keep_dst(dev);