[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170421.153635.1878323052363882645.davem@davemloft.net>
Date: Fri, 21 Apr 2017 15:36:35 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: nikolay@...ulusnetworks.com
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
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?
Powered by blists - more mailing lists