From: Tom Stellard <tstellar@redhat.com>
To: sedat.dilek@gmail.com
Cc: Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
dwarves@vger.kernel.org, bpf@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andriin@fb.com>, Yonghong Song <yhs@fb.com>,
Hao Luo <haoluo@google.com>
Subject: Re: [PATCH] btf_encoder: Add extra checks for symbol names
Date: Thu, 14 Jan 2021 06:33:44 -0800 [thread overview]
Message-ID: <dae1ec1e-7d19-e4c6-891b-ab774486dbee@redhat.com> (raw)
In-Reply-To: <CA+icZUV9rdRuswqDa9u=VFcqgHp1x+jmz565QCFi=yC0D7hhVQ@mail.gmail.com>
On 1/13/21 11:50 PM, Sedat Dilek wrote:
> On Wed, Jan 13, 2021 at 1:28 AM Tom Stellard <tstellar@redhat.com> wrote:
>>
>> On 1/12/21 10:40 AM, Jiri Olsa wrote:
>>> When processing kernel image build by clang we can
>>> find some functions without the name, which causes
>>> pahole to segfault.
>>>
>>> Adding extra checks to make sure we always have
>>> function's name defined before using it.
>>>
>>
>> I backported this patch to pahole 1.19, and I can confirm it fixes the
>> segfault for me.
>>
>
> Thanks for testing.
>
> Can you give me Git commit-id of LLVM-12 you tried?
>
I was building with LLVM 11.0.1
-Tom
> - Sedat -
>
>> -Tom
>>
>>> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
>>> ---
>>> btf_encoder.c | 8 ++++++--
>>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/btf_encoder.c b/btf_encoder.c
>>> index 333973054b61..17f7a14f2ef0 100644
>>> --- a/btf_encoder.c
>>> +++ b/btf_encoder.c
>>> @@ -72,6 +72,8 @@ static int collect_function(struct btf_elf *btfe, GElf_Sym *sym)
>>>
>>> if (elf_sym__type(sym) != STT_FUNC)
>>> return 0;
>>> + if (!elf_sym__name(sym, btfe->symtab))
>>> + return 0;
>>>
>>> if (functions_cnt == functions_alloc) {
>>> functions_alloc = max(1000, functions_alloc * 3 / 2);
>>> @@ -730,9 +732,11 @@ int cu__encode_btf(struct cu *cu, int verbose, bool force,
>>> if (!has_arg_names(cu, &fn->proto))
>>> continue;
>>> if (functions_cnt) {
>>> - struct elf_function *func;
>>> + const char *name = function__name(fn, cu);
>>> + struct elf_function *func = NULL;
>>>
>>> - func = find_function(btfe, function__name(fn, cu));
>>> + if (name)
>>> + func = find_function(btfe, name);
>>> if (!func || func->generated)
>>> continue;
>>> func->generated = true;
>>>
>>
>
next prev parent reply other threads:[~2021-01-14 14:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 18:40 [PATCH] btf_encoder: Add extra checks for symbol names Jiri Olsa
2021-01-12 19:20 ` Andrii Nakryiko
2021-01-12 19:47 ` Jiri Olsa
2021-01-12 20:17 ` Sedat Dilek
2021-01-13 0:27 ` Tom Stellard
2021-01-14 7:50 ` Sedat Dilek
2021-01-14 14:33 ` Tom Stellard [this message]
2021-01-14 14:39 ` Sedat Dilek
2021-01-21 13:38 ` Arnaldo Carvalho de Melo
2021-01-21 16:06 ` Sedat Dilek
2021-01-21 19:37 ` Arnaldo Carvalho de Melo
2021-01-21 20:53 ` Andrii Nakryiko
2021-01-22 2:07 ` Sedat Dilek
2021-01-22 4:11 ` Andrii Nakryiko
2021-01-28 20:00 ` [RFT] pahole 1.20 RC was " Arnaldo Carvalho de Melo
2021-01-28 20:57 ` Sedat Dilek
2021-01-28 21:11 ` Arnaldo Carvalho de Melo
2021-01-28 22:28 ` Sedat Dilek
2021-02-02 7:48 ` Andrii Nakryiko
2021-02-03 9:03 ` Sedat Dilek
2021-02-03 10:23 ` Mark Wielaard
2021-02-03 21:48 ` Sedat Dilek
2021-02-03 23:21 ` Andrii Nakryiko
2021-02-04 1:06 ` Arnaldo Carvalho de Melo
2021-02-04 6:40 ` Sedat Dilek
2021-01-21 17:37 ` Tom Stellard
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=dae1ec1e-7d19-e4c6-891b-ab774486dbee@redhat.com \
--to=tstellar@redhat.com \
--cc=acme@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=haoluo@google.com \
--cc=jolsa@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).