From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
ojeda@kernel.org, andrii.nakryiko@gmail.com, jolsa@kernel.org,
dwarves@vger.kernel.org, stephen.s.brennan@oracle.com
Subject: Re: [PATCH dwarves] btf_encoder: filter var names before btf name check
Date: Tue, 22 Oct 2024 15:39:31 -0300 [thread overview]
Message-ID: <ZxfxY44iOJCcuNhU@x1> (raw)
In-Reply-To: <CANiq72kMif-BzsNwmh8WpDgc_KohxkHZA2=+F6RjEKV+j8TnmQ@mail.gmail.com>
On Tue, Oct 22, 2024 at 08:21:09PM +0200, Miguel Ojeda wrote:
> On Fri, Oct 18, 2024 at 11:43 AM Alan Maguire <alan.maguire@oracle.com> wrote:
> >
> > ...as this means we avoid seeing multiple messages of the form
> >
> > PAHOLE: Warning: Found invalid variable name when encoding btf, ignored (sym: '__UNIQUE_ID___addressable__RNvXsa_NtCs2vSfyxKMEZc_4core4charNtB5_11EscapeDebugNtNtNtNtB7_4iter6traits10exact_size17ExactSizeIterator3len57').
> >
> > Such symbols are filtered anyway due to the __UNIQUE_ID prefix, so
> > warning about them is not necessary; simply reordering the checks
> > should ensure we will not see these warnings.
> >
> > Reported-by: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
>
> FWIW, I applied the patch and the `__UNIQUE_ID` warnings indeed go
> away (but I don't know if those warnings would be useful to see/fix
> for other reasons):
Maybe we should have a debug mode where anything that is skipped gets
reported.
> Tested-by: Miguel Ojeda <ojeda@kernel.org>
Thanks, since this hasn't hit 'master' yet, I added it to the cset,
- Arnaldo
next prev parent reply other threads:[~2024-10-22 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 9:43 [PATCH dwarves] btf_encoder: filter var names before btf name check Alan Maguire
2024-10-22 18:21 ` Miguel Ojeda
2024-10-22 18:39 ` Arnaldo Carvalho de Melo [this message]
2024-10-22 22:17 ` Stephen Brennan
2024-10-23 14:24 ` Arnaldo Carvalho de Melo
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=ZxfxY44iOJCcuNhU@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=stephen.s.brennan@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox