[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164931061239.16262.17688495506884085480.git-patchwork-notify@kernel.org>
Date: Thu, 07 Apr 2022 05:50:12 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Niels Dossche <dossche.niels@...il.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
davem@...emloft.net, yoshfuji@...ux-ipv6.org, dsahern@...nel.org,
kuba@...nel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next v2] ipv6: fix locking issues with loops over
idev->addr_list
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
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
Powered by blists - more mailing lists