public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
	andrii@kernel.org, martin.lau@kernel.org, daniel@iogearbox.net,
	memxor@gmail.com, eddyz87@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1 0/2] Allow referenced dynptr to be overwritten when siblings exists
Date: Wed, 08 Apr 2026 01:30:29 +0000	[thread overview]
Message-ID: <177561182979.28494.17307819279533756669.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260406150548.1354271-1-ameryhung@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon,  6 Apr 2026 08:05:46 -0700 you wrote:
> The patchset conditionally allow a referenced dynptr to be overwritten
> when its siblings (original dynptr or dynptr clone) exist. Do it before
> the verifier relation tracking refactor to mimimize verifier changes at
> a time.
> 
> Amery Hung (2):
>   bpf: Allow overwriting referenced dynptr when refcnt > 1
>   selftests/bpf: Test overwriting referenced dynptr
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1,1/2] bpf: Allow overwriting referenced dynptr when refcnt > 1
    https://git.kernel.org/bpf/bpf-next/c/017f5c4ef73c
  - [bpf-next,v1,2/2] selftests/bpf: Test overwriting referenced dynptr
    https://git.kernel.org/bpf/bpf-next/c/4cfb09a38357

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-04-08  1:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 15:05 [PATCH bpf-next v1 0/2] Allow referenced dynptr to be overwritten when siblings exists Amery Hung
2026-04-06 15:05 ` [PATCH bpf-next v1 1/2] bpf: Allow overwriting referenced dynptr when refcnt > 1 Amery Hung
2026-04-07 15:51   ` Kumar Kartikeya Dwivedi
2026-04-07 21:27   ` Alexei Starovoitov
2026-04-07 22:05     ` Amery Hung
2026-04-07 22:13       ` Kumar Kartikeya Dwivedi
2026-04-06 15:05 ` [PATCH bpf-next v1 2/2] selftests/bpf: Test overwriting referenced dynptr Amery Hung
2026-04-07 15:58   ` Kumar Kartikeya Dwivedi
2026-04-08  1:30 ` 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=177561182979.28494.17307819279533756669.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    /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