[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44095170-e47c-ce85-d0f6-95a24da0e200@cumulusnetworks.com>
Date: Fri, 21 Apr 2017 22:50:35 +0300
From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
To: David Miller <davem@...emloft.net>
Cc: netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org,
dvyukov@...gle.com, kcc@...gle.com, syzkaller@...glegroups.com,
edumazet@...gle.com, roopa@...ulusnetworks.com,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] ip6mr: fix notification device destruction
On 21/04/17 22:36, David Miller wrote:
> From: Nikolay Aleksandrov <nikolay@...ulusnetworks.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?
>
Good question, AFAICS since ip6mr exists because it was copied from ipmr:
commit 7bc570c8b4f7
Author: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
Date: Thu Apr 3 09:22:53 2008 +0900
[IPV6] MROUTE: Support multicast forwarding.
Powered by blists - more mailing lists