[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173384943076.907573.13245503646453425882.git-patchwork-notify@kernel.org>
Date: Tue, 10 Dec 2024 16:50:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Michal Luczaj <mhal@...x.co>
Cc: andrii@...nel.org, eddyz87@...il.com, mykolal@...com, ast@...nel.org,
daniel@...earbox.net, martin.lau@...ux.dev, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, shuah@...nel.org,
jakub@...udflare.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org, bpf@...r.kernel.org,
linux-kselftest@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH bpf 0/3] bpf, sockmap: Fix the element replace
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Mon, 02 Dec 2024 12:29:22 +0100 you wrote:
> Series takes care of two issues with sockmap update: inconsistent behaviour
> after update with same, and race/refcount imbalance on element replace.
>
> I am hesitant if patch 3/3 ("bpf, sockmap: Fix race between element replace
> and close()") is the right approach. I might have missed some detail of the
> current __sock_map_delete() implementation. I'd be grateful for comments,
> thanks.
>
> [...]
Here is the summary with links:
- [bpf,1/3] bpf, sockmap: Fix update element with same
https://git.kernel.org/bpf/bpf/c/75e072a390da
- [bpf,2/3] selftest/bpf: Extend test for sockmap update with same
https://git.kernel.org/bpf/bpf/c/11d5245f608f
- [bpf,3/3] bpf, sockmap: Fix race between element replace and close()
https://git.kernel.org/bpf/bpf/c/ed1fc5d76b81
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