From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, chenyuan@kylinos.cn, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
emil@etsalapatis.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf] bpf: Hold map BTF for the memory allocator destructor record
Date: Fri, 25 Sep 2026 17:30:12 +0000 [thread overview]
Message-ID: <179035741215.3062647.1669325075936587788.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925064652.2261885-1-memxor@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 25 Sep 2026 08:46:51 +0200 you wrote:
> bpf_ma_set_dtor() duplicates map->record so that the bpf_mem_alloc
> destructor can release the special fields of hash and rhash map elements
> once the allocator frees them for good. btf_record_dup() only acquires
> references on kernel and module BTF. Fields whose types live in the map
> BTF keep pointing into it: a kptr to a local type refers to map->btf,
> and a list_head or rb_root field carries a value_rec owned by the struct
> meta table of map->btf.
>
> [...]
Here is the summary with links:
- [bpf] bpf: Hold map BTF for the memory allocator destructor record
https://git.kernel.org/bpf/bpf/c/ab39974240a0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-25 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 6:46 [PATCH bpf] bpf: Hold map BTF for the memory allocator destructor record Kumar Kartikeya Dwivedi
2026-09-25 17:30 ` 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=179035741215.3062647.1669325075936587788.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=chenyuan@kylinos.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.