public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qi Tang <tpluszz77@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
	eddyz87@gmail.com, andrii@kernel.org, martin.lau@linux.dev,
	john.fastabend@gmail.com, song@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf v4 0/2] bpf: reject direct access to nullable PTR_TO_BUF pointers
Date: Fri, 03 Apr 2026 15:27:45 +0000	[thread overview]
Message-ID: <177523006579.1344849.13798536246638210752.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260403033828.18529-1-tpluszz77@gmail.com>

Hello:

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

On Fri,  3 Apr 2026 11:38:26 +0800 you wrote:
> check_mem_access() allows direct dereference of PTR_TO_BUF |
> PTR_MAYBE_NULL without a null check, causing kernel NULL dereference
> on map iterator stop callbacks.
> 
> Patch 1 adds the missing type_may_be_null() guard.
> Patch 2 adds a selftest with a test runner.
> 
> [...]

Here is the summary with links:
  - [bpf,v4,1/2] bpf: reject direct access to nullable PTR_TO_BUF pointers
    https://git.kernel.org/bpf/bpf-next/c/b0db1accbc73
  - [bpf,v4,2/2] selftests/bpf: add test for nullable PTR_TO_BUF access
    (no matching commit)

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-03 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03  3:38 [PATCH bpf v4 0/2] bpf: reject direct access to nullable PTR_TO_BUF pointers Qi Tang
2026-04-03  3:38 ` [PATCH bpf v4 1/2] " Qi Tang
2026-04-03  6:16   ` Amery Hung
2026-04-03  3:38 ` [PATCH bpf v4 2/2] selftests/bpf: add test for nullable PTR_TO_BUF access Qi Tang
2026-04-03  6:16   ` Amery Hung
2026-04-06 20:13     ` Kumar Kartikeya Dwivedi
2026-04-07 13:42       ` Qi Tang
2026-04-03 15: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=177523006579.1344849.13798536246638210752.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=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --cc=tpluszz77@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