From: Yonghong Song <yonghong.song@linux.dev>
To: Sami Tolvanen <samitolvanen@google.com>, bpf@vger.kernel.org
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 4/4] bpf, btf: Enforce destructor kfunc type with CFI
Date: Fri, 25 Jul 2025 16:37:42 -0700 [thread overview]
Message-ID: <41b23698-b577-4dcc-ae43-6a7d5294dd9c@linux.dev> (raw)
In-Reply-To: <20250725214401.1475224-10-samitolvanen@google.com>
On 7/25/25 2:44 PM, Sami Tolvanen wrote:
> Ensure that registered destructor kfuncs have the same type
> as btf_dtor_kfunc_t to avoid a kernel panic on systems with
> CONFIG_CFI_CLANG enabled.
>
> Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
next prev parent reply other threads:[~2025-07-25 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 21:44 [PATCH bpf-next v2 0/4] Use correct destructor kfunc types Sami Tolvanen
2025-07-25 21:44 ` [PATCH bpf-next v2 1/4] bpf: crypto: Use the correct destructor kfunc type Sami Tolvanen
2025-07-25 23:11 ` Yonghong Song
2025-07-28 18:18 ` Sami Tolvanen
2025-07-25 21:44 ` [PATCH bpf-next v2 2/4] bpf: net_sched: " Sami Tolvanen
2025-07-25 21:44 ` [PATCH bpf-next v2 3/4] selftests/bpf: " Sami Tolvanen
2025-07-25 21:44 ` [PATCH bpf-next v2 4/4] bpf, btf: Enforce destructor kfunc type with CFI Sami Tolvanen
2025-07-25 23:37 ` Yonghong Song [this message]
2025-07-25 23:42 ` [PATCH bpf-next v2 0/4] Use correct destructor kfunc types Yonghong Song
2025-07-28 18:21 ` Sami Tolvanen
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=41b23698-b577-4dcc-ae43-6a7d5294dd9c@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=xiyou.wangcong@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.