From: Ian Rogers <irogers@google.com>
To: 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>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Swapnil Sapkal <swapnil.sapkal@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] perf header: Fix memory corruption and unnecessary warning
Date: Thu, 10 Sep 2026 14:12:17 -0700 [thread overview]
Message-ID: <20260910211221.3154261-1-irogers@google.com> (raw)
In-Reply-To: <20260910175634.3014018-1-irogers@google.com>
Some minor fixes that have shown up during testing.
v3: Fix Sashiko include nit. Accidentally posted wrong 1st patch in v2 (sorry :-( )
v2: Fix missing newling for pr_warning:
https://lore.kernel.org/linux-perf-users/20260910175634.3014018-1-irogers@google.com/
v1:
https://lore.kernel.org/linux-perf-users/20260910173715.2996571-1-irogers@google.com/
Ian Rogers (3):
perf header: Fix HEADER_COMPRESSED validation for comp_mmap_len
perf header: Fix potential memory corruption in cpu_cache_level__read
perf header: Transition WARN macros to debug.h equivalents
tools/perf/util/header.c | 122 ++++++++++++++++++++++++---------------
1 file changed, 74 insertions(+), 48 deletions(-)
--
2.55.0.1007.g17ff1f9808-goog
next prev parent reply other threads:[~2026-09-10 21:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 17:37 [PATCH v1 1/3] perf header: Fix HEADER_COMPRESSED validation for comp_mmap_len Ian Rogers
2026-09-10 17:37 ` [PATCH v1 2/3] perf header: Fix potential memory corruption in cpu_cache_level__read Ian Rogers
2026-09-10 17:47 ` sashiko-bot
2026-09-10 17:37 ` [PATCH v1 3/3] perf header: Transition WARN macros to debug.h equivalents Ian Rogers
2026-09-10 17:46 ` sashiko-bot
2026-09-10 17:51 ` [PATCH v1 1/3] perf header: Fix HEADER_COMPRESSED validation for comp_mmap_len sashiko-bot
2026-09-10 17:56 ` [PATCH v2 1/3] perf test x86: Fix missing __msan_unpoison Ian Rogers
2026-09-10 17:56 ` [PATCH v2 2/3] perf header: Fix HEADER_COMPRESSED validation for comp_mmap_len Ian Rogers
2026-09-10 18:14 ` sashiko-bot
2026-09-10 17:56 ` [PATCH v2 3/3] perf header: Fix potential memory corruption in cpu_cache_level__read Ian Rogers
2026-09-10 18:08 ` sashiko-bot
2026-09-10 18:11 ` [PATCH v2 1/3] perf test x86: Fix missing __msan_unpoison sashiko-bot
2026-09-10 21:12 ` Ian Rogers [this message]
2026-09-10 21:12 ` [PATCH v3 1/3] perf header: Fix HEADER_COMPRESSED validation for comp_mmap_len Ian Rogers
2026-09-10 21:21 ` sashiko-bot
2026-09-10 21:12 ` [PATCH v3 2/3] perf header: Fix potential memory corruption in cpu_cache_level__read Ian Rogers
2026-09-10 21:22 ` sashiko-bot
2026-09-10 21:12 ` [PATCH v3 3/3] perf header: Transition WARN macros to debug.h equivalents Ian Rogers
2026-09-10 21:18 ` sashiko-bot
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=20260910211221.3154261-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=james.clark@linaro.org \
--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=peterz@infradead.org \
--cc=swapnil.sapkal@amd.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