BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tao Chen <chen.dylane@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
	sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 1/3] bpf: Add lookup_and_delete_elem for BPF_MAP_STACK_TRACE
Date: Thu, 25 Sep 2025 23:20:08 +0000	[thread overview]
Message-ID: <175884240831.3555731.6888839221416950805.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250925175030.1615837-1-chen.dylane@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.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@linux.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



      parent reply	other threads:[~2025-09-25 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 17:50 [PATCH bpf-next v6 1/3] bpf: Add lookup_and_delete_elem for BPF_MAP_STACK_TRACE Tao Chen
2025-09-25 17:50 ` [PATCH bpf-next v6 2/3] selftests/bpf: Refactor stacktrace_map case with skeleton Tao Chen
2025-09-25 23:18   ` Andrii Nakryiko
2025-09-25 17:50 ` [PATCH bpf-next v6 3/3] selftests/bpf: Add stacktrace map lookup_and_delete_elem test case Tao Chen
2025-09-25 23:20 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=175884240831.3555731.6888839221416950805.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chen.dylane@linux.dev \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox