All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yiyang Chen <chenyy23@mails.tsinghua.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, john.fastabend@gmail.com,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, emil@etsalapatis.com, shuah@kernel.org,
	vmalik@redhat.com, leon.hwang@linux.dev, davemarchevsky@fb.com,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/2] bpf: Reject offset refcount acquire arguments
Date: Fri, 26 Jun 2026 12:27:57 +0000	[thread overview]
Message-ID: <178247687731.457674.9945546096682680522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1782192383.git.chenyy23@mails.tsinghua.edu.cn>

Hello:

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

On Tue, 23 Jun 2026 06:11:08 +0000 you wrote:
> bpf_refcount_acquire() is modeled as returning a refcounted allocation
> base, but it currently accepts PTR_TO_BTF_ID | MEM_ALLOC arguments whose
> offset already points at an embedded graph node returned from a list or
> rbtree operation.
> 
> At runtime the kfunc starts from the supplied pointer and adds the type's
> refcount offset. With a graph-node pointer, that starts from base +
> node_off, while the verifier treats the returned pointer as the allocation
> base. Reject non-zero fixed-offset arguments to keep the runtime operation
> and the verifier model aligned.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] bpf: Reject offset refcount acquire arguments
    https://git.kernel.org/bpf/bpf/c/931a577fc79e
  - [bpf-next,v4,2/2] selftests/bpf: Cover refcount acquire node offsets
    https://git.kernel.org/bpf/bpf/c/0371fb57a0c9

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-06-26 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  6:11 [PATCH bpf-next v4 0/2] bpf: Reject offset refcount acquire arguments Yiyang Chen
2026-06-23  6:11 ` [PATCH bpf-next v4 1/2] " Yiyang Chen
2026-06-23  7:01   ` bot+bpf-ci
2026-06-23 21:52     ` Emil Tsalapatis
2026-06-25 21:30   ` Yonghong Song
2026-06-23  6:11 ` [PATCH bpf-next v4 2/2] selftests/bpf: Cover refcount acquire node offsets Yiyang Chen
2026-06-23 21:50   ` Emil Tsalapatis
2026-06-25 21:39   ` Yonghong Song
2026-06-26 12:27 ` 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=178247687731.457674.9945546096682680522.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=chenyy23@mails.tsinghua.edu.cn \
    --cc=daniel@iogearbox.net \
    --cc=davemarchevsky@fb.com \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=leon.hwang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=vmalik@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.