From: Namhyung Kim <namhyung@kernel.org>
To: Triet Hoang <triet.hoang.dev@gmail.com>
Cc: sashiko-bot@kernel.org, linux-perf-users@vger.kernel.org,
sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH v2] perf unwind: handle allocation failure in libdw__get_entries()
Date: Sat, 29 Aug 2026 13:42:20 -0700 [thread overview]
Message-ID: <apNELHaLHzBrPwrd@google.com> (raw)
In-Reply-To: <20260818144837.741469-1-triet.hoang.dev@gmail.com>
On Tue, Aug 18, 2026 at 02:48:37PM +0000, Triet Hoang wrote:
> Check the return value of zalloc() before dereferencing the allocated
> dwfl_ui_ti structure.
>
> Return -ENOMEM when the allocation fails to avoid a NULL pointer
> dereference.
>
> Signed-off-by: Triet Hoang <triet.hoang.dev@gmail.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> Changes in v2:
> - Free the ui structure before returning -ENOMEM to avoid memory leak.
> ---
> tools/perf/util/unwind-libdw.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tools/perf/util/unwind-libdw.c b/tools/perf/util/unwind-libdw.c
> index 7f35042be567..fd8a5125468c 100644
> --- a/tools/perf/util/unwind-libdw.c
> +++ b/tools/perf/util/unwind-libdw.c
> @@ -379,6 +379,11 @@ int libdw__get_entries(unwind_entry_cb_t cb, void *arg,
> dwfl = dwfl_ui_ti->dwfl;
> } else {
> dwfl_ui_ti = zalloc(sizeof(*dwfl_ui_ti));
> + if (!dwfl_ui_ti) {
> + free(ui);
> + return -ENOMEM;
> + }
> +
> dwfl = dwfl_begin(&offline_callbacks);
> if (!dwfl)
> goto out;
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-08-29 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 14:24 [PATCH] perf unwind: handle allocation failure in libdw__get_entries() Triet Hoang
2026-08-18 14:29 ` sashiko-bot
2026-08-18 14:48 ` [PATCH v2] " Triet Hoang
2026-08-18 14:59 ` sashiko-bot
2026-08-18 19:24 ` Markus Elfring
2026-08-29 20:42 ` Namhyung Kim [this message]
2026-09-08 21:51 ` 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=apNELHaLHzBrPwrd@google.com \
--to=namhyung@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=triet.hoang.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.