From: ihor.solodrai@linux.dev
To: alan.maguire@oracle.com, acme@kernel.org
Cc: eddyz87@gmail.com, andrii@kernel.org, mykolal@fb.com,
bpf@vger.kernel.org, dwarves@vger.kernel.org
Subject: Re: [PATCH dwarves v2] btf_encoder: fix memory access bugs
Date: Tue, 28 Jan 2025 00:03:05 +0000 [thread overview]
Message-ID: <8bb182c6a5f7a7ac3668297bca5a31467fac93de@linux.dev> (raw)
In-Reply-To: <20241216183112.206072-1-ihor.solodrai@pm.me>
December 16, 2024 at 10:31 AM, "Ihor Solodrai" <ihor.solodrai@pm.me> wrote:
>
> When compiled with address sanitizer, a couple of errors were reported
>
> on pahole BTF encoding:
>
> * A memory leak of strdup(func->alias), due to unchecked
>
> reassignment.
>
> * A read of uninitialized memory in gobuffer__sort or bsearch in
>
> case btf_funcs gobuffer is empty.
>
> Used compiler flags:
>
> -fsanitize=undefined,address
>
> -fsanitize-recover=address
>
> -fno-omit-frame-pointer
>
> v1: https://lore.kernel.org/dwarves/20241213233205.633927-1-ihor.solodrai@pm.me/
>
> Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
>
> Signed-off-by: Ihor Solodrai <ihor.solodrai@pm.me>
>
> ---
>
> btf_encoder.c | 11 +++++++++--
>
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
Alan, Arnaldo,
This patch hasn't been applied.
Just a reminder in case it fell off the radar.
Thanks.
next prev parent reply other threads:[~2025-01-28 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 18:31 [PATCH dwarves v2] btf_encoder: fix memory access bugs Ihor Solodrai
2025-01-28 0:03 ` ihor.solodrai [this message]
2025-01-31 13:14 ` Alan Maguire
2025-01-31 22:41 ` Ihor Solodrai
2025-03-12 16:52 ` Alan Maguire
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=8bb182c6a5f7a7ac3668297bca5a31467fac93de@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--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