BPF List
 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, daniel@iogearbox.net, eddyz87@gmail.com,
	memxor@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v2 1/2] bpf: Reject passing scalar NULL to nonnull arg of a global subprog
Date: Thu, 23 Jul 2026 23:20:07 +0000	[thread overview]
Message-ID: <178484880790.2910968.7200730529599928400.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723221815.367797-1-ameryhung@gmail.com>

Hello:

This series was applied to bpf/bpf.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:

On Thu, 23 Jul 2026 15:18:14 -0700 you wrote:
> A global subprogram argument tagged __arg_nonnull is set up as a
> non-nullable PTR_TO_MEM. However the verifier does not check against a
> scalar NULL, leading to real NULL pointer dereference. Reject it as
> well.
> 
> Fixes: 94e1c70a3452 ("bpf: support 'arg:xxx' btf_decl_tag-based hints for global subprog args")
> Acked-by: Eduard Zingerman <eddyz87@gmail.com>
> Signed-off-by: Amery Hung <ameryhung@gmail.com>
> 
> [...]

Here is the summary with links:
  - [bpf,v2,1/2] bpf: Reject passing scalar NULL to nonnull arg of a global subprog
    https://git.kernel.org/bpf/bpf/c/289e680c89ae
  - [bpf,v2,2/2] selftests/bpf: Test passing scalar NULL to nonnull global subprog
    https://git.kernel.org/bpf/bpf/c/55c7bd2ddee5

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-07-23 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 22:18 [PATCH bpf v2 1/2] bpf: Reject passing scalar NULL to nonnull arg of a global subprog Amery Hung
2026-07-23 22:18 ` [PATCH bpf v2 2/2] selftests/bpf: Test passing scalar NULL to nonnull " Amery Hung
2026-07-23 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=178484880790.2910968.7200730529599928400.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=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