From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net] ipv6: mcast: better catch silly mtu values
Date: Wed, 13 Dec 2017 13:17:07 -0500 (EST)
Message-ID: <20171213.131707.1750188618556965595.davem@davemloft.net>
References: <CADvbK_cnxEgU--FO+ATGL+fe2z59XVzRGzKxp1-vZxL8x8LmKA@mail.gmail.com>
        <1512838770.25033.33.camel@gmail.com>
        <1513004618.25033.43.camel@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: lucien.xin@gmail.com, netdev@vger.kernel.org
To: eric.dumazet@gmail.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:42088 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753011AbdLMSRO (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 13 Dec 2017 13:17:14 -0500
In-Reply-To: <1513004618.25033.43.camel@gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 11 Dec 2017 07:03:38 -0800

> From: Eric Dumazet <edumazet@google.com>
> 
> syzkaller reported crashes in IPv6 stack [1]
> 
> Xin Long found that lo MTU was set to silly values.
> 
> IPv6 stack reacts to changes to small MTU, by disabling itself under
> RTNL.
> 
> But there is a window where threads not using RTNL can see a wrong
> device mtu. This can lead to surprises, in mld code where it is assumed
> the mtu is suitable.
> 
> Fix this by reading device mtu once and checking IPv6 minimal MTU.
 ...
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Reported-by: syzbot <syzkaller@googlegroups.com>

Applied and queued up for -stable.