BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
	tj@kernel.org, ameryhung@gmail.com, kkd@meta.com,
	kernel-team@meta.com
Subject: Re: [PATCH bpf-next v5 00/11] Fix generic __uninit kfunc output buffers
Date: Mon, 21 Sep 2026 17:20:08 +0000	[thread overview]
Message-ID: <179001120864.3142019.5279636337497659902.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921023843.411943-1-memxor@gmail.com>

Hello:

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

On Mon, 21 Sep 2026 04:38:24 +0200 you wrote:
> Generic __uninit kfunc arguments are output buffers. Stack liveness treats
> them as writes, but argument checking still requires readable contents and
> does not record definite initialization after the call. Check these
> arguments as write-only and record privileged output initialization after
> validating all inputs, including inputs that alias an output.
> 
> Following Eduard's rework, helpers and kfuncs record generic outputs in the
> same argument-checking path after type resolution. Generated kfunc
> prototypes now mark generic buffers with MEM_WRITE, so __uninit buffers are
> checked as write-only ahead of the fix while ordinary buffers stay
> read/write.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,01/11] selftests/bpf: Allow privileged preparation for capability tests
    https://git.kernel.org/bpf/bpf-next/c/06046a8a50e8
  - [bpf-next,v5,02/11] bpf: Record raw memory arguments during argument checking
    https://git.kernel.org/bpf/bpf-next/c/e2b4aaa75040
  - [bpf-next,v5,03/11] bpf: Check __uninit kfunc output buffers as write-only
    https://git.kernel.org/bpf/bpf-next/c/fc8dc2be101b
  - [bpf-next,v5,04/11] bpf: Fix generic __uninit kfunc output buffers
    https://git.kernel.org/bpf/bpf-next/c/fc670d4b6c31
  - [bpf-next,v5,05/11] selftests/bpf: Cover generic __uninit output initialization
    https://git.kernel.org/bpf/bpf-next/c/a8bbd9ee1bbc
  - [bpf-next,v5,06/11] bpf: Support multiple __uninit kfunc output arguments
    https://git.kernel.org/bpf/bpf-next/c/bca730ba6df6
  - [bpf-next,v5,07/11] selftests/bpf: Cover __uninit kfunc output argument slots
    https://git.kernel.org/bpf/bpf-next/c/89835699ef4e
  - [bpf-next,v5,08/11] bpf: Preserve stack initialization for generic output buffers
    https://git.kernel.org/bpf/bpf-next/c/5da4a9f26fca
  - [bpf-next,v5,09/11] selftests/bpf: Cover generic output stack initialization
    https://git.kernel.org/bpf/bpf-next/c/a25a61385b04
  - [bpf-next,v5,10/11] bpf: Check read access for helper input/output buffers
    https://git.kernel.org/bpf/bpf-next/c/7a6cef39b760
  - [bpf-next,v5,11/11] selftests/bpf: Cover helper memory access permissions
    https://git.kernel.org/bpf/bpf-next/c/ad36589c3f39

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-09-21 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  2:38 [PATCH bpf-next v5 00/11] Fix generic __uninit kfunc output buffers Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 01/11] selftests/bpf: Allow privileged preparation for capability tests Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 02/11] bpf: Record raw memory arguments during argument checking Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 03/11] bpf: Check __uninit kfunc output buffers as write-only Kumar Kartikeya Dwivedi
2026-09-21  3:54   ` bot+bpf-ci
2026-09-21  2:38 ` [PATCH bpf-next v5 04/11] bpf: Fix generic __uninit kfunc output buffers Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 05/11] selftests/bpf: Cover generic __uninit output initialization Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 06/11] bpf: Support multiple __uninit kfunc output arguments Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 07/11] selftests/bpf: Cover __uninit kfunc output argument slots Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 08/11] bpf: Preserve stack initialization for generic output buffers Kumar Kartikeya Dwivedi
2026-09-21  3:54   ` bot+bpf-ci
2026-09-21  2:38 ` [PATCH bpf-next v5 09/11] selftests/bpf: Cover generic output stack initialization Kumar Kartikeya Dwivedi
2026-09-21  3:54   ` bot+bpf-ci
2026-09-21  2:38 ` [PATCH bpf-next v5 10/11] bpf: Check read access for helper input/output buffers Kumar Kartikeya Dwivedi
2026-09-21  2:38 ` [PATCH bpf-next v5 11/11] selftests/bpf: Cover helper memory access permissions Kumar Kartikeya Dwivedi
2026-09-21  3:54   ` bot+bpf-ci
2026-09-21 17: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=179001120864.3142019.5279636337497659902.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=emil@etsalapatis.com \
    --cc=kernel-team@meta.com \
    --cc=kkd@meta.com \
    --cc=memxor@gmail.com \
    --cc=tj@kernel.org \
    /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