[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175884240831.3555731.6888839221416950805.git-patchwork-notify@kernel.org>
Date: Thu, 25 Sep 2025 23:20:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Tao Chen <chen.dylane@...ux.dev>
Cc: ast@...nel.org, daniel@...earbox.net, john.fastabend@...il.com,
andrii@...nel.org, martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v6 1/3] bpf: Add lookup_and_delete_elem for
BPF_MAP_STACK_TRACE
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Fri, 26 Sep 2025 01:50:28 +0800 you wrote:
> The stacktrace map can be easily full, which will lead to failure in
> obtaining the stack. In addition to increasing the size of the map,
> another solution is to delete the stack_id after looking it up from
> the user, so extend the existing bpf_map_lookup_and_delete_elem()
> functionality to stacktrace map types.
>
> Signed-off-by: Tao Chen <chen.dylane@...ux.dev>
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/3] bpf: Add lookup_and_delete_elem for BPF_MAP_STACK_TRACE
https://git.kernel.org/bpf/bpf-next/c/17f0d1f6321c
- [bpf-next,v6,2/3] selftests/bpf: Refactor stacktrace_map case with skeleton
(no matching commit)
- [bpf-next,v6,3/3] selftests/bpf: Add stacktrace map lookup_and_delete_elem test case
https://git.kernel.org/bpf/bpf-next/c/d43029ff7d1b
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