Date: Fri, 21 Apr 2017 15:36:35 -0400 (EDT)
Message-Id: <20170421.153635.1878323052363882645.davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org, dvyukov@google.com,
        kcc@google.com, syzkaller@googlegroups.com, edumazet@google.com,
        roopa@cumulusnetworks.com, torvalds@linux-foundation.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ip6mr: fix notification device destruction
From: David Miller <davem@davemloft.net>
In-Reply-To: <6d7dca26-4bc6-870c-8eb9-409f6c6b8fd5@cumulusnetworks.com>
References: <CAAeHK+zUZMGQuW=7Qhz3EWYjh6Zwv9eMBCiMCU79QrYNWox0-Q@mail.gmail.com>
        <1492796536-28781-1-git-send-email-nikolay@cumulusnetworks.com>
        <6d7dca26-4bc6-870c-8eb9-409f6c6b8fd5@cumulusnetworks.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 677
Lines: 16

From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date: Fri, 21 Apr 2017 21:30:42 +0300

> On 21/04/17 20:42, Nikolay Aleksandrov wrote:
>> Andrey Konovalov reported a BUG caused by the ip6mr code which is caused
>> because we call unregister_netdevice_many for a device that is already
>> being destroyed. In IPv4's ipmr that has been resolved by two commits
>> long time ago by introducing the "notify" parameter to the delete
>> function and avoiding the unregister when called from a notifier, so
>> let's do the same for ip6mr.
 ...
> +CC LKML and Linus

Applied, thanks Nikolay and thanks Andrey for the report and testing.

Nikolay, how far does this bug go back?