From: James Clark <james.clark@linaro.org>
To: Ian Rogers <irogers@google.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf tests kallsyms: Fix missed map__put
Date: Fri, 12 Dec 2025 17:19:47 +0200 [thread overview]
Message-ID: <e0410f42-f70d-464e-82aa-7237d779ba6b@linaro.org> (raw)
In-Reply-To: <20251210190141.12725-1-irogers@google.com>
On 10/12/2025 21:01, Ian Rogers wrote:
> Issue was caught by leak sanitizer and the test robot.
>
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202512101502.f3819cd3-lkp@intel.com
> Fixes: 34e271ae5538 ("perf test: Add kallsyms split test")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/tests/kallsyms-split.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/tests/kallsyms-split.c b/tools/perf/tests/kallsyms-split.c
> index bbbc66957e5d..117ed3b70f63 100644
> --- a/tools/perf/tests/kallsyms-split.c
> +++ b/tools/perf/tests/kallsyms-split.c
> @@ -148,6 +148,7 @@ static int test__kallsyms_split(struct test_suite *test __maybe_unused,
> ret = TEST_OK;
>
> out:
> + map__put(map);
> remove_proc_dir(0);
> machine__exit(&m);
> return ret;
Reviewed-by: James Clark <james.clark@linaro.org>
prev parent reply other threads:[~2025-12-12 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 19:01 [PATCH v1] perf tests kallsyms: Fix missed map__put Ian Rogers
2025-12-12 15:19 ` James Clark [this message]
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=e0410f42-f70d-464e-82aa-7237d779ba6b@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
/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).