BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xu Yunxiang <xyx2021@mail.ustc.edu.cn>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
	ameryhung@gmail.com, sashiko-bot@kernel.org
Subject: Re: [PATCH bpf-next v6 0/2] bpf: Destroy callee-local dynptrs on subprog return
Date: Mon, 05 Oct 2026 23:40:05 +0000	[thread overview]
Message-ID: <179124360578.1939764.3003662912880693578.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260927120422.1042107-1-xyx2021@mail.ustc.edu.cn>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Sun, 27 Sep 2026 20:04:20 +0800 you wrote:
> A dynptr data slice is valid only while the specific dynptr that produced
> it remains valid. Apply normal dynptr stack-slot teardown before a callee
> frame disappears, so its descendants are invalidated and its last
> release-capable referenced dynptr cannot be lost.
> 
> Patch 1 adds a helper to destroy dynptrs in an inclusive range of stack
> slots and reuses it for initialization, variable-offset writes and
> subprogram returns. The callback diagnostic expectation changes in that
> same commit. Patch 2 tests callee-local slices, last-holder rejection and
> caller-owned slice compatibility.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/2] bpf: Track borrowed iterator results by default
    (no matching commit)
  - [bpf-next,v6,2/2] selftests/bpf: Test dynptr teardown on subprog return
    https://git.kernel.org/bpf/bpf-next/c/b04ba9375a9e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-05 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 12:04 [PATCH bpf-next v6 0/2] bpf: Destroy callee-local dynptrs on subprog return Xu Yunxiang
2026-09-27 12:04 ` [PATCH bpf-next v6 1/2] " Xu Yunxiang
2026-09-28  4:48   ` Amery Hung
2026-10-02 11:29     ` Alexei Starovoitov
2026-10-05 21:59       ` Ihor Solodrai
2026-10-05 22:33         ` Amery Hung
2026-09-27 12:04 ` [PATCH bpf-next v6 2/2] selftests/bpf: Test dynptr teardown " Xu Yunxiang
2026-09-28  5:24   ` Amery Hung
2026-10-05 23:40 ` 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=179124360578.1939764.3003662912880693578.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=memxor@gmail.com \
    --cc=sashiko-bot@kernel.org \
    --cc=xyx2021@mail.ustc.edu.cn \
    /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