From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: <chenyuan_fl@163.com>, <bpf@vger.kernel.org>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Yuan Chen" <chenyuan@kylinos.cn>
Subject: Re: [PATCH bpf-next 0/2] bpf: Cancel special fields in resizable hashtab on recycle
Date: Tue, 11 Aug 2026 16:22:31 +0200 [thread overview]
Message-ID: <DKM6K95EN9OF.3O9XNYWVLYHDE@gmail.com> (raw)
In-Reply-To: <20260811095531.3294167-1-chenyuan_fl@163.com>
On Tue Aug 11, 2026 at 11:55 AM CEST, chenyuan_fl wrote:
> From: Yuan Chen <chenyuan@kylinos.cn>
>
> The resizable hashtab (BPF_MAP_TYPE_RHASH) still eagerly calls
> bpf_obj_free_fields() when an element is deleted or its value is
> replaced, which runs kptr destructors in the caller's execution context.
> This is unsafe for BPF programs running in NMI context (e.g. perf_event
> programs attached to hardware PMU overflows), where referenced kptr
> destructors may take locks or otherwise cannot run.
>
> Commit a3a81d247651 ("bpf: Cancel special fields on map value recycle")
> switched the hash map and array recycle paths to bpf_obj_cancel_fields(),
> which only cancels NMI-safe fields (timer, workqueue, task_work), but it
> missed the resizable hashtab. Patch 1 applies the same semantics to
> rhtab; patch 2 adds a regression test.
>
> Yuan Chen (2):
> bpf: Cancel special fields in resizable hashtab on recycle
> selftests/bpf: Test rhtab kptr recycle from NMI context
>
At least go through the mailing list before sending patches.
https://lore.kernel.org/bpf/DKEVG8ZVJDDQ.2G40FTOIZKU57@gmail.com
pw-bot: cr
> kernel/bpf/hashtab.c | 28 +++--
> .../selftests/bpf/prog_tests/rhtab_kptr.c | 87 +++++++++++++++
> .../testing/selftests/bpf/progs/rhtab_kptr.c | 101 ++++++++++++++++++
> 3 files changed, 207 insertions(+), 9 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/rhtab_kptr.c
> create mode 100644 tools/testing/selftests/bpf/progs/rhtab_kptr.c
next prev parent reply other threads:[~2026-08-11 14:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 9:55 [PATCH bpf-next 0/2] bpf: Cancel special fields in resizable hashtab on recycle chenyuan_fl
2026-08-11 9:55 ` [PATCH bpf-next 1/2] " chenyuan_fl
2026-08-11 10:50 ` bot+bpf-ci
2026-08-11 9:55 ` [PATCH bpf-next 2/2] selftests/bpf: Test rhtab kptr recycle from NMI context chenyuan_fl
2026-08-11 11:08 ` bot+bpf-ci
2026-08-11 14:22 ` Kumar Kartikeya Dwivedi [this message]
2026-08-24 14:36 ` [PATCH bpf-next v2 0/4] bpf: Cancel special fields in resizable hashtab on recycle chenyuan_fl
2026-08-24 14:36 ` [PATCH 1/4] " chenyuan_fl
2026-08-24 15:00 ` sashiko-bot
2026-08-24 15:42 ` bot+bpf-ci
2026-08-24 16:15 ` Mykyta Yatsenko
2026-08-24 14:36 ` [PATCH 2/4] bpf: Fix use-after-free of program BTF in mem-alloc destructor chenyuan_fl
2026-08-24 15:17 ` sashiko-bot
2026-08-24 15:42 ` bot+bpf-ci
2026-08-24 14:36 ` [PATCH 3/4] selftests/bpf: Test rhtab kptr recycle from NMI context chenyuan_fl
2026-08-24 15:28 ` sashiko-bot
2026-08-24 15:42 ` bot+bpf-ci
2026-08-24 14:36 ` [PATCH 4/4] selftests/bpf: Test rhtab special-field combinations chenyuan_fl
2026-08-24 15:40 ` sashiko-bot
2026-08-24 15:42 ` bot+bpf-ci
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=DKM6K95EN9OF.3O9XNYWVLYHDE@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyuan@kylinos.cn \
--cc=chenyuan_fl@163.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@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