Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
	shuah@kernel.org, yatsenko@meta.com, alan.maguire@oracle.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf v4 0/5] bpf: Fix NULL-ptr-derefs when showing a void BTF type
Date: Thu, 03 Sep 2026 16:40:14 +0000	[thread overview]
Message-ID: <178845361464.3438810.12687597306930362552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260901104924.346187-1-jiayuan.chen@linux.dev>

Hello:

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

On Tue,  1 Sep 2026 18:47:34 +0800 you wrote:
> This series fixes three NULL-ptr-derefs in BTF handling.
> 
> Patch 1 handles the syzbot report. A key-less BTF (btf_key_type_id == 0) used
> to be rejected for hash maps, until htab and rhtab gained a ->map_check_btf
> (to register a dtor) that does not look at the key, so a key-less hash map is
> now accepted. Dumping it through bpffs feeds the key type_id 0 into
> btf_type_seq_show() and NULL-derefs in btf_type_show(). Reject it again.
> 
> [...]

Here is the summary with links:
  - [bpf,v4,1/5] bpf: Reject key-less BTF for hash maps
    https://git.kernel.org/bpf/bpf/c/0895a0c07347
  - [bpf,v4,2/5] bpf: Fix NULL-ptr-deref when showing a void BTF type
    https://git.kernel.org/bpf/bpf/c/4ea508b9ebd7
  - [bpf,v4,3/5] bpf: Fix NULL-ptr-deref in btf_var_show()
    https://git.kernel.org/bpf/bpf/c/5403a383f52f
  - [bpf,v4,4/5] selftests/bpf: Add test for key-less BTF hash map
    https://git.kernel.org/bpf/bpf/c/6265b44f2c3b
  - [bpf,v4,5/5] selftests/bpf: Add test for showing a void BTF type
    https://git.kernel.org/bpf/bpf/c/1ae6aa61958a

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-03 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 10:47 [PATCH bpf v4 0/5] bpf: Fix NULL-ptr-derefs when showing a void BTF type Jiayuan Chen
2026-09-01 10:47 ` [PATCH bpf v4 1/5] bpf: Reject key-less BTF for hash maps Jiayuan Chen
2026-09-01 10:47 ` [PATCH bpf v4 2/5] bpf: Fix NULL-ptr-deref when showing a void BTF type Jiayuan Chen
2026-09-01 10:47 ` [PATCH bpf v4 3/5] bpf: Fix NULL-ptr-deref in btf_var_show() Jiayuan Chen
2026-09-01 10:47 ` [PATCH bpf v4 4/5] selftests/bpf: Add test for key-less BTF hash map Jiayuan Chen
2026-09-01 10:47 ` [PATCH bpf v4 5/5] selftests/bpf: Add test for showing a void BTF type Jiayuan Chen
2026-09-03 16:40 ` 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=178845361464.3438810.12687597306930362552.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.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=ihor.solodrai@linux.dev \
    --cc=jiayuan.chen@linux.dev \
    --cc=jolsa@kernel.org \
    --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=yatsenko@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox