[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161765280968.6353.18220031386238138462.git-patchwork-notify@kernel.org>
Date: Mon, 05 Apr 2021 20:00:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Taehee Yoo <ap420073@...il.com>
Cc: davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
edumazet@...gle.com, yoshfuji@...ux-ipv6.org, dsahern@...nel.org,
jmaloy@...hat.com, ying.xue@...driver.com,
tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH v2 net-next] mld: change lockdep annotation for
ip6_sf_socklist and ipv6_mc_socklist
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sun, 4 Apr 2021 13:38:23 +0000 you wrote:
> struct ip6_sf_socklist and ipv6_mc_socklist are per-socket MLD data.
> These data are protected by rtnl lock, socket lock, and RCU.
> So, when these are used, it verifies whether rtnl lock is acquired or not.
>
> ip6_mc_msfget() is called by do_ipv6_getsockopt().
> But caller doesn't acquire rtnl lock.
> So, when these data are used in the ip6_mc_msfget() lockdep warns about it.
> But accessing these is actually safe because socket lock was acquired by
> do_ipv6_getsockopt().
>
> [...]
Here is the summary with links:
- [v2,net-next] mld: change lockdep annotation for ip6_sf_socklist and ipv6_mc_socklist
https://git.kernel.org/netdev/net-next/c/4b4b84468aa2
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