mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Ian Rogers <irogers@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	James Clark <james.clark@linaro.org>,
	<linux-perf-users@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan Liang <kan.liang@linux.intel.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v3 2/2] perf test: Add sched latency and script shell tests
Date: Sun, 20 Jul 2025 16:35:03 +0800	[thread overview]
Message-ID: <202507201046.5842fe9a-lkp@intel.com> (raw)
In-Reply-To: <20250628012302.1242532-2-irogers@google.com>


Hello,

kernel test robot noticed "kmsg.sanitizer.direct_leak/__interceptor_realloc" on:

commit: 738c34064b92cfb47180911f409e393e78a96818 ("[PATCH v3 2/2] perf test: Add sched latency and script shell tests")
url: https://github.com/intel-lab-lkp/linux/commits/Ian-Rogers/perf-test-Add-sched-latency-and-script-shell-tests/20250628-092510
base: https://git.kernel.org/cgit/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/all/20250628012302.1242532-2-irogers@google.com/
patch subject: [PATCH v3 2/2] perf test: Add sched latency and script shell tests

in testcase: perf-sanity-tests
version: 
with following parameters:

	perf_compiler: clang
	group: group-01



config: x86_64-rhel-9.4-bpf
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby Lake) with 32G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)




If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202507201046.5842fe9a-lkp@intel.com



2025-07-10 21:48:29 sudo /usr/src/linux-perf-x86_64-rhel-9.4-bpf-738c34064b92cfb47180911f409e393e78a96818/tools/perf/perf test 91 -v
 91: perf sched tests                                                : Running (1 active)
--- start ---
test child forked, pid 10659
Sched latency
pid 10663's current affinity list: 0-7
pid 10663's new affinity list: 0
pid 10665's current affinity list: 0-7
pid 10665's new affinity list: 0
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.335 MB /tmp/__perf_test_sched.perf.data.1IqjN (1973 samples) ]

=================================================================
==10672==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 67 byte(s) in 1 object(s) allocated from:
    #0 0x7fdf4ada98d5 in __interceptor_realloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:85
    #1 0x7fdf4a2723e1  (/lib/x86_64-linux-gnu/libc.so.6+0x7e3e1)
    #2 0x4f63ab0b0c0befff  (<unknown module>)

SUMMARY: AddressSanitizer: 67 byte(s) leaked in 1 allocation(s).
Unexpected signal in test_sched_latency
---- end(-1) ----
 91: perf sched tests                                                : FAILED!



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250720/202507201046.5842fe9a-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  reply	other threads:[~2025-07-20  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28  1:23 [PATCH v3 1/2] perf test workload noploop: Name the noploop process Ian Rogers
2025-06-28  1:23 ` [PATCH v3 2/2] perf test: Add sched latency and script shell tests Ian Rogers
2025-07-20  8:35   ` kernel test robot [this message]
2025-07-02 16:43 ` [PATCH v3 1/2] perf test workload noploop: Name the noploop process Namhyung Kim

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=202507201046.5842fe9a-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --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

all inboxes | Powered by JetHome®