From: Eduard Zingerman <eddyz87@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>,
Yonghong Song <yonghong.song@linux.dev>,
Andrea Righi <arighi@nvidia.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
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>,
David Vernet <void@manifault.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: Mark kfuncs as __noclone
Date: Wed, 27 Aug 2025 12:41:15 -0700 [thread overview]
Message-ID: <0d5c5cf8e1f3efb35b1f597dae2ae2bf0fb9a346.camel@gmail.com> (raw)
In-Reply-To: <c41268ae-e09c-43e3-9bd3-89b762989ec0@oracle.com>
On Wed, 2025-08-27 at 20:28 +0100, Alan Maguire wrote:
[...]
> I'm working on a small 2-patch series at the moment to improve this. The
> problem is we currently have no way to associate the DWARF with the
> relevant ELF function; DWARF representations of functions do not have
> "." suffixes either so we are just matching by name prefix when we
> collect DWARF info about a particular function.
Oh, I see, there is no way to associate DWARF info with either
'bpf_strnchr' or 'bpf_strnchr.constprop.0' w/o checking address.
Thank you.
> The series I'm working on uses DWARF addresses to improve the DWARF/ELF
> association, ensuring that we don't toss functions that look
> inconsistent but just have .part or .cold suffixed components that have
> non-matching DWARF function signatures. ".constprop" isn't covered yet
> however.
Is ".constprop" special, or just has to be allowed as one of the prefixes?
[...]
next prev parent reply other threads:[~2025-08-27 19:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 14:05 [PATCH] bpf: Mark kfuncs as __noclone Andrea Righi
2025-08-26 20:17 ` Yonghong Song
2025-08-27 5:02 ` Eduard Zingerman
2025-08-27 5:41 ` Andrea Righi
2025-08-27 6:52 ` Eduard Zingerman
2025-08-27 7:01 ` Eduard Zingerman
2025-08-27 7:45 ` Andrea Righi
2025-08-27 17:03 ` Yonghong Song
2025-08-27 17:00 ` Yonghong Song
2025-08-27 19:13 ` Eduard Zingerman
2025-08-27 19:28 ` Alan Maguire
2025-08-27 19:41 ` Eduard Zingerman [this message]
2025-08-27 19:52 ` Alan Maguire
2025-08-27 22:28 ` Yonghong Song
2025-08-27 22:10 ` Yonghong Song
2025-08-27 2:10 ` David Vernet
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=0d5c5cf8e1f3efb35b1f597dae2ae2bf0fb9a346.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--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=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=void@manifault.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;
as well as URLs for NNTP newsgroup(s).