From: Sami Tolvanen <samitolvanen@google.com>
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, 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 0/4] Use correct destructor kfunc types
Date: Mon, 28 Jul 2025 18:21:34 +0000 [thread overview]
Message-ID: <20250728182134.GB899009@google.com> (raw)
In-Reply-To: <5d7d1ff3-14cd-4c18-a180-3c99e784bbeb@linux.dev>
On Fri, Jul 25, 2025 at 04:42:29PM -0700, Yonghong Song wrote:
>
> With this patch set and no CONFIG_CFI_CLANG in .config,
> the bpf selftests work okay. In bpf ci, CONFIG_CFI_CLANG
> is not enabled.
>
> But if enabling CONFIG_CFI_CLANG, this patch set fixed
> ./test_progs run issue, but there are some test failures
> like
>
> ===
> test_get_linfo:FAIL:check jited_linfo[1]:ffffffffa000d581 - ffffffffa000d558 > 39
> processed 4 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
> #32/186 btf/line_info (No subprog):FAIL
>
> test_get_linfo:FAIL:check jited_linfo[1]:ffffffffa000dee5 - ffffffffa000debc > 39
> processed 4 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
> #32/189 btf/line_info (No subprog. zero tailing line_info:FAIL
>
> ...
>
> test_get_linfo:FAIL:check jited_linfo[1]:ffffffffa000e069 - ffffffffa000e040 > 38
> processed 9 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0
> #32/202 btf/line_info (dead subprog + dead start w/ move):FAIL
> #32 btf:FAIL
> ===
>
> The failure probably not related to this patch, but rather related
> to CONFIG_CFI_CLANG itself. I will debug this separately.
Agreed, that looks unrelated to this series.
Sami
prev parent reply other threads:[~2025-07-28 18:21 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
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 [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=20250728182134.GB899009@google.com \
--to=samitolvanen@google.com \
--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=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=xiyou.wangcong@gmail.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 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.