Re: [PATCH net-next v2] ipv6: fix locking issues with loops over idev->addr_list

[patchwork-bot+netdevbpf]

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@xxxxxxxxxx>:

On Mon,  4 Apr 2022 01:15:24 +0200 you wrote:
> idev->addr_list needs to be protected by idev->lock. However, it is not
> always possible to do so while iterating and performing actions on
> inet6_ifaddr instances. For example, multiple functions (like
> addrconf_{join,leave}_anycast) eventually call down to other functions
> that acquire the idev->lock. The current code temporarily unlocked the
> idev->lock during the loops, which can cause race conditions. Moving the
> locks up is also not an appropriate solution as the ordering of lock
> acquisition will be inconsistent with for example mc_lock.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] ipv6: fix locking issues with loops over idev->addr_list
    https://git.kernel.org/netdev/net-next/c/51454ea42c1a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html