| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAH0uvoiF0OYWd9fB7_XxwK_pScYASnTNGssv2ABp1xcdz=+1nA@mail.gmail.com>
Date: Fri, 13 Jun 2025 09:16:12 -0700
From: Howard Chu <howardchu95@...il.com>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org, acme@...nel.org, mingo@...hat.com,
namhyung@...nel.org, mark.rutland@....com, alexander.shishkin@...ux.intel.com,
jolsa@...nel.org, irogers@...gle.com, adrian.hunter@...el.com,
peterz@...radead.org, kan.liang@...ux.intel.com
Subject: Re: [PATCH v3 5/6] perf test trace BTF: Use --sort-events in BTF
general tests
On Fri, Jun 13, 2025 at 2:41 AM kernel test robot <oliver.sang@...el.com> wrote:
>
>
> Hello,
>
> besides below formal report, we observed below difference comparing to parent.
>
> 1d2859b4fa79a8e2 609a86901e6fd886f1139aed8f8
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :6 100% 6:6 kmsg.sanitizer.direct_leak/__interceptor_malloc/alloc_event/ordered_events__new_event/ordered_events__queue/trace__deliver_event/trace__run
> :6 100% 6:6 kmsg.sanitizer.direct_leak/__interceptor_malloc/thread__get/trace__sys_enter/trace__handle_event/__trace__deliver_event/ordered_events__deliver_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/nsinfo__alloc/nsinfo__copy/map__new/machine__process_mmap2_event/machine__process_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/comm__new/thread__new/threads__findnew/__machine__findnew_thread
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/dso__new_id/__dsos__addnew_id/__dsos__findnew_id/dsos__findnew_id
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/dso__new_id/dso__new/__machine__addnew_vdso/machine__findnew_vdso
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/map__new/machine__process_mmap2_event/machine__process_event/trace__process_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/maps__new/thread__init_maps/__machine__findnew_thread/machine__findnew_thread
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/thread__new/threads__findnew/__machine__findnew_thread/machine__findnew_thread
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_calloc/zalloc/thread_trace__new/thread__trace/trace__sys_enter/trace__handle_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/comm_str__get/comm_strs__findnew/comm__override/____thread__set_comm/__thread__set_comm
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/dso__get/map__init/map__new/machine__process_mmap2_event/machine__process_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/map__get/__maps__insert_sorted/__maps__fixup_overlap_and_insert/maps__fixup_overlap_and_insert/thread__insert_map
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/maps__new/thread__init_maps/__machine__findnew_thread/machine__findnew_thread/machine__process_comm_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/nsinfo__alloc/nsinfo__copy/map__new/machine__process_mmap2_event/machine__process_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/nsinfo__alloc/nsinfo__new/thread__new/threads__findnew/__machine__findnew_thread
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/nsinfo__get/map__new/machine__process_mmap2_event/machine__process_event/trace__process_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_malloc/trace__sys_enter/trace__handle_event/__trace__deliver_event/ordered_events__deliver_event/do_flush
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_realloc/__maps__insert_sorted/__maps__fixup_overlap_and_insert/maps__fixup_overlap_and_insert/thread__insert_map/machine__process_mmap2_event
> :6 100% 6:6 kmsg.sanitizer.indirect_leak/__interceptor_strdup/dso__set_basename/__dsos__addnew_id/__dsos__findnew_id/dsos__findnew_id/machine__findnew_dso_id
>
>
> we don't have enough knowledge whether the appearance of these leak message is
> actually a fix from 609a86901e6fd886f1139aed8f8 which allows to show issue
> clearly. so just report out FYI.
>
> below is formal report.
>
>
> kernel test robot noticed "kmsg.sanitizer.indirect_leak/__interceptor_malloc/trace__sys_enter/trace__handle_event/__trace__deliver_event/ordered_events__deliver_event/do_flush" on:
>
> commit: 609a86901e6fd886f1139aed8f8c66d982f2afed ("[PATCH v3 5/6] perf test trace BTF: Use --sort-events in BTF general tests")
> url: https://github.com/intel-lab-lkp/linux/commits/Howard-Chu/perf-test-trace-Use-shell-s-f-flag-to-check-if-vmlinux-exists/20250529-031444
> patch link: https://lore.kernel.org/all/20250528191148.89118-6-howardchu95@gmail.com/
> patch subject: [PATCH v3 5/6] perf test trace BTF: Use --sort-events in BTF general tests
Definitely because of --sort-event, option coverage is important. Will
fix it, thanks bot.
Powered by blists - more mailing lists