From: Eduard Zingerman <eddyz87@gmail.com>
To: Ihor Solodrai <ihor.solodrai@pm.me>,
dwarves@vger.kernel.org, acme@kernel.org
Cc: bpf@vger.kernel.org, alan.maguire@oracle.com, andrii@kernel.org,
mykolal@fb.com
Subject: Re: [RFC PATCH 8/9] btf_encoder: introduce btf_encoding_context
Date: Fri, 29 Nov 2024 15:12:37 -0800 [thread overview]
Message-ID: <e1df45360963d265ea5e0b3634f0a3dae0c9c343.camel@gmail.com> (raw)
In-Reply-To: <20241128012341.4081072-9-ihor.solodrai@pm.me>
On Thu, 2024-11-28 at 01:24 +0000, Ihor Solodrai wrote:
Note, after applying this patch I see the following report from
address sanitizer:
Direct leak of 3640 byte(s) in 1 object(s) allocated from:
#0 0x7f12d2ac2290 in calloc (/lib64/libasan.so.8+0xc2290) (BuildId: ...)
#1 0x478775 in btf_encoder__new /home/eddy/work/dwarves-fork/btf_encoder.c:2562
#2 0x416f98 in pahole_stealer /home/eddy/work/dwarves-fork/pahole.c:3257
#3 0x49f9b9 in cu__finalize /home/eddy/work/dwarves-fork/dwarf_loader.c:3263
Which points to line:
encoder->secinfo = calloc(encoder->seccnt, sizeof(*encoder->secinfo));
(when compiled with the following flags:
-fsanitize=undefined,address -fsanitize-recover=address -fno-omit-frame-pointer)
[...]
> @@ -1355,19 +1400,15 @@ int btf_encoder__add_saved_funcs(struct btf_encoder *encoder)
Nit: should probably remove 'encoder' parameter and replace it with
bool skip_encoding_inconsistent_proto
(in one of the earlier patches, just noticed this).
> list_for_each_entry(s, &e->func_states, node)
> nr_saved_fns++;
> }
> - /* Another thread already did this work */
> - if (nr_saved_fns == 0) {
> - printf("nothing to do for encoder...\n");
> +
> + if (nr_saved_fns == 0)
> return 0;
> - }
>
> - printf("got %d saved functions...\n", nr_saved_fns);
> saved_fns = calloc(nr_saved_fns, sizeof(*saved_fns));
> btf_encoders__for_each_encoder(e) {
> list_for_each_entry(s, &e->func_states, node)
> saved_fns[i++] = s;
> }
> - printf("added %d saved fns\n", i);
> qsort(saved_fns, nr_saved_fns, sizeof(*saved_fns), saved_functions_cmp);
>
> for (i = 0; i < nr_saved_fns; i = j) {
[...]
next prev parent reply other threads:[~2024-11-29 23:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 1:23 [RFC PATCH 0/9] pahole: shared ELF and faster reproducible BTF encoding Ihor Solodrai
2024-11-28 1:23 ` [RFC PATCH 1/9] btf_encoder: simplify function encoding Ihor Solodrai
2024-11-29 8:16 ` Eduard Zingerman
2024-12-02 13:55 ` Jiri Olsa
2024-11-28 1:23 ` [RFC PATCH 2/9] btf_encoder: store,use section-relative addresses in ELF function representation Ihor Solodrai
2024-11-29 9:07 ` Eduard Zingerman
2024-12-02 14:34 ` Alan Maguire
2024-11-28 1:23 ` [RFC PATCH 3/9] btf_encoder: separate elf function, saved function representations Ihor Solodrai
2024-11-29 20:37 ` Eduard Zingerman
2024-12-09 21:19 ` Ihor Solodrai
2024-11-28 1:24 ` [RFC PATCH 4/9] dwarf_loader: introduce pre_load_module hook to conf_load Ihor Solodrai
2024-11-29 21:03 ` Eduard Zingerman
2024-11-28 1:24 ` [RFC PATCH 5/9] btf_encoder: introduce elf_functions struct type Ihor Solodrai
2024-11-29 21:50 ` Eduard Zingerman
2024-11-28 1:24 ` [RFC PATCH 6/9] btf_encoder: collect elf_functions in btf_encoder__pre_load_module Ihor Solodrai
2024-11-29 22:27 ` Eduard Zingerman
2024-11-28 1:24 ` [RFC PATCH 7/9] btf_encoder: switch to shared elf_functions table Ihor Solodrai
2024-11-29 22:35 ` Eduard Zingerman
2024-12-09 23:55 ` Ihor Solodrai
2024-11-28 1:24 ` [RFC PATCH 8/9] btf_encoder: introduce btf_encoding_context Ihor Solodrai
2024-11-29 23:12 ` Eduard Zingerman [this message]
2024-11-28 1:24 ` [RFC PATCH 9/9] pahole: faster reproducible BTF encoding Ihor Solodrai
2024-11-30 0:17 ` Eduard Zingerman
2024-12-02 13:55 ` [RFC PATCH 0/9] pahole: shared ELF and " Jiri Olsa
2024-12-06 18:19 ` Ihor Solodrai
2024-12-06 18:30 ` 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=e1df45360963d265ea5e0b3634f0a3dae0c9c343.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=ihor.solodrai@pm.me \
--cc=mykolal@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