[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168134281755.14415.12895311674672248237.git-patchwork-notify@kernel.org>
Date: Wed, 12 Apr 2023 23:40:17 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Xin Liu <liuxin350@...wei.com>
Cc: andrii@...nel.org, ast@...nel.org, daniel@...earbox.net,
martin.lau@...ux.dev, song@...nel.org, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
haoluo@...gle.com, jolsa@...nel.org, bpf@...r.kernel.org,
hsinweih@....edu, linux-kernel@...r.kernel.org, yanan@...wei.com,
wuchangye@...wei.com, xiesongyang@...wei.com,
kongweibin2@...wei.com, zhangmingyi5@...wei.com
Subject: Re: [PATCH bpf-next] bpf,
sockmap: fix deadlocks in the sockhash and sockmap
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Thu, 6 Apr 2023 20:26:22 +0800 you wrote:
> When huang uses sched_switch tracepoint, the tracepoint
> does only one thing in the mounted ebpf program, which
> deletes the fixed elements in sockhash ([0])
>
> It seems that elements in sockhash are rarely actively
> deleted by users or ebpf program. Therefore, we do not
> pay much attention to their deletion. Compared with hash
> maps, sockhash only provides spin_lock_bh protection.
> This causes it to appear to have self-locking behavior
> in the interrupt context.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, sockmap: fix deadlocks in the sockhash and sockmap
https://git.kernel.org/bpf/bpf-next/c/ed17aa92dc56
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