From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: bot+bpf-ci@kernel.org, jiayuan.chen@linux.dev, bpf@vger.kernel.org
Cc: syzbot+37b56485bbbf90ad8489@syzkaller.appspotmail.com,
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,
martin.lau@kernel.org, mason@kernel.org
Subject: Re: [PATCH bpf v3 1/5] bpf: Reject key-less BTF for hash maps
Date: Mon, 31 Aug 2026 20:27:11 +0800 [thread overview]
Message-ID: <309536ab-86b3-47a6-a420-c460447f6c46@linux.dev> (raw)
In-Reply-To: <9ed4c84cc7d723627f10b9b5d1dafb9b72d3e0bcff6db149d7605f5d9ad8c7b1@mail.kernel.org>
在 8/31/26 8:05 PM, bot+bpf-ci@kernel.org 写道:
>> map_check_btf() allows a key-less BTF (btf_key_type_id == 0) only for
>> maps that have a ->map_check_btf callback, and leaves the actual
>> decision to that callback. Hash maps used to have no ->map_check_btf,
>> so a key-less BTF was rejected outright.
>>
>> That changed when htab and rhtab gained a ->map_check_btf to register a
>> dtor - htab in commit 1df97a7453ee ("bpf: Register dtor for freeing
>> special fields") and rhtab in commit 6905f8601298 ("bpf: Allow special
>> fields in resizable hashtab"). Neither looks at the key, so a key-less
>> hash map now passes map_check_btf() and gets created. Reading it back
>> through bpffs feeds the key type_id 0 into btf_type_seq_show();
>> btf_type_by_id() returns the void type, kind_ops[BTF_KIND_UNKN] is NULL,
>> and btf_type_show() dereferences it:
>>
>> KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
>> RIP: 0010:btf_type_show+0x223/0x2e0 kernel/bpf/btf.c:8232
>> Call Trace:
>> <TASK>
>> btf_type_seq_show_flags+0xca/0x120 kernel/bpf/btf.c:8250
>> htab_map_seq_show_elem+0x12e/0x350 kernel/bpf/hashtab.c:1669
>> map_seq_show+0x13d/0x1e0 kernel/bpf/inode.c:293
>> seq_read_iter+0x93f/0x1270 fs/seq_file.c:196
>> seq_read+0x344/0x4d0 fs/seq_file.c:163
>> vfs_read+0x1e4/0xb40 fs/read_write.c:572
>> __x64_sys_pread64+0x1eb/0x250 fs/read_write.c:769
>> do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
>> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>> </TASK>
> The call trace appears to be edited from the original syzbot report.
> The original report (6a8f4e88.27659fcc.2ceef7.0008.GAE@google.com)
> includes these additional frames between map_seq_show and seq_read_iter:
>
> traverse.part.0.constprop.0+0x107/0x650 fs/seq_file.c:112
> traverse fs/seq_file.c:99 [inline]
>
> and also includes the inline frames for the pread64 syscall path:
>
> ksys_pread64 fs/read_write.c:760 [inline]
> __do_sys_pread64 fs/read_write.c:769 [inline]
> __se_sys_pread64 fs/read_write.c:766 [inline]
I edited it intentionally to avoid breaking the format rule.
next prev parent reply other threads:[~2026-08-31 12:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 11:01 [PATCH bpf v3 0/5] bpf: Fix NULL-ptr-derefs when showing a void BTF type Jiayuan Chen
2026-08-31 11:01 ` [PATCH bpf v3 1/5] bpf: Reject key-less BTF for hash maps Jiayuan Chen
2026-08-31 12:05 ` bot+bpf-ci
2026-08-31 12:27 ` Jiayuan Chen [this message]
2026-08-31 21:01 ` Ihor Solodrai
2026-08-31 11:01 ` [PATCH bpf v3 2/5] bpf: Fix NULL-ptr-deref when showing a void BTF type Jiayuan Chen
2026-08-31 11:48 ` bot+bpf-ci
2026-08-31 12:48 ` Jiayuan Chen
2026-08-31 21:06 ` Ihor Solodrai
2026-08-31 11:01 ` [PATCH bpf v3 3/5] bpf: Fix NULL-ptr-deref in btf_var_show() Jiayuan Chen
2026-08-31 21:08 ` Ihor Solodrai
2026-08-31 11:01 ` [PATCH bpf v3 4/5] selftests/bpf: Add test for key-less BTF hash map Jiayuan Chen
2026-08-31 11:48 ` bot+bpf-ci
2026-08-31 12:54 ` Jiayuan Chen
2026-08-31 21:12 ` Ihor Solodrai
2026-08-31 11:01 ` [PATCH bpf v3 5/5] selftests/bpf: Add test for showing a void BTF type Jiayuan Chen
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=309536ab-86b3-47a6-a420-c460447f6c46@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@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=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mason@kernel.org \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=syzbot+37b56485bbbf90ad8489@syzkaller.appspotmail.com \
--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