[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174113883377.363569.807347823586416499.git-patchwork-notify@kernel.org>
Date: Wed, 05 Mar 2025 01:40:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Matthieu Baerts <matttbe@...nel.org>
Cc: mptcp@...ts.linux.dev, martineau@...nel.org, geliang@...nel.org,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
horms@...nel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kjlx@...pleofstupid.com, stable@...r.kernel.org
Subject: Re: [PATCH net] mptcp: fix 'scheduling while atomic' in
mptcp_pm_nl_append_new_local_addr
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Mon, 03 Mar 2025 18:10:13 +0100 you wrote:
> From: Krister Johansen <kjlx@...pleofstupid.com>
>
> If multiple connection requests attempt to create an implicit mptcp
> endpoint in parallel, more than one caller may end up in
> mptcp_pm_nl_append_new_local_addr because none found the address in
> local_addr_list during their call to mptcp_pm_nl_get_local_id. In this
> case, the concurrent new_local_addr calls may delete the address entry
> created by the previous caller. These deletes use synchronize_rcu, but
> this is not permitted in some of the contexts where this function may be
> called. During packet recv, the caller may be in a rcu read critical
> section and have preemption disabled.
>
> [...]
Here is the summary with links:
- [net] mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr
https://git.kernel.org/netdev/net/c/022bfe24aad8
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