public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, acme@kernel.org,
	namhyung@kernel.org, james.clark@linaro.org, irogers@google.com
Cc: agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com,
	Thomas Richter <tmricht@linux.ibm.com>
Subject: [PATCH linux-next] perf parse-events: Fix big-endian 'overwrite' by writing correct union member
Date: Thu, 12 Feb 2026 13:53:15 +0100	[thread overview]
Message-ID: <20260212125315.777356-1-tmricht@linux.ibm.com> (raw)

The "Read backward ring buffer" test crashes on big-endian (e.g. s390x)
due to a NULL dereference when the backward mmap path isn't enabled.

Reproducer:
  # ./perf test -F 'Read backward ring buffer'
  Segmentation fault (core dumped)
  # uname -m
  s390x
  #

Root cause:
get_config_terms() stores into evsel_config_term::val.val (u64) while later
code reads boolean fields such as evsel_config_term::val.overwrite.
On big-endian the 1-byte boolean is left-aligned, so writing
evsel_config_term::val.val = 1 is read back as
evsel_config_term::val.overwrite = 0,
leaving backward mmap disabled and a NULL map being used.

Store values in the union member that matches the term type, e.g.:
  /* for OVERWRITE */
  new_term->val.overwrite = 1;  /* not new_term->val.val = 1 */
to fix this.

Impact:
Enables backward mmap on big-endian and prevents the crash.
No change on little-endian.

Output after:
 # ./perf test -Fv 44
 --- start ---
 Using CPUID IBM,9175,705,ME1,3.8,002f
 mmap size 1052672B
 mmap size 8192B
 ---- end ----
 44: Read backward ring buffer                         : Ok
 #

Fixes: 159ca97cd97c ("perf parse-events: Refactor get_config_terms() to remove macros")
Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
Reviewed-by: Jan Polensky <japo@linux.ibm.com>
Cc: James Clark <james.clark@linaro.org>
Cc: Ian Rogers <irogers@google.com>
---
 tools/perf/util/parse-events.c | 49 +++++++++++++++++++++++++++++++++-
 1 file changed, 48 insertions(+), 1 deletion(-)

diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
index d4647ded340f..12fe5392c832 100644
--- a/tools/perf/util/parse-events.c
+++ b/tools/perf/util/parse-events.c
@@ -1250,7 +1250,54 @@ static int get_config_terms(const struct parse_events_terms *head_config,
 			}
 			new_term->free_str = true;
 		} else {
-			new_term->val.val = val;
+			switch (new_type) {
+			case EVSEL__CONFIG_TERM_PERIOD:
+				new_term->val.period = val;
+				break;
+			case EVSEL__CONFIG_TERM_FREQ:
+				new_term->val.freq = val;
+				break;
+			case EVSEL__CONFIG_TERM_TIME:
+				new_term->val.time = val;
+				break;
+			case EVSEL__CONFIG_TERM_STACK_USER:
+				new_term->val.stack_user = val;
+				break;
+			case EVSEL__CONFIG_TERM_INHERIT:
+				new_term->val.inherit = val;
+				break;
+			case EVSEL__CONFIG_TERM_OVERWRITE:
+				new_term->val.overwrite = val;
+				break;
+			case EVSEL__CONFIG_TERM_MAX_STACK:
+				new_term->val.max_stack = val;
+				break;
+			case EVSEL__CONFIG_TERM_MAX_EVENTS:
+				new_term->val.max_events = val;
+				break;
+			case EVSEL__CONFIG_TERM_PERCORE:
+				new_term->val.percore = val;
+				break;
+			case EVSEL__CONFIG_TERM_AUX_OUTPUT:
+				new_term->val.aux_output = val;
+				break;
+			case EVSEL__CONFIG_TERM_AUX_SAMPLE_SIZE:
+				new_term->val.aux_sample_size = val;
+				break;
+			case EVSEL__CONFIG_TERM_CALLGRAPH:
+			case EVSEL__CONFIG_TERM_DRV_CFG:
+			case EVSEL__CONFIG_TERM_BRANCH:
+			case EVSEL__CONFIG_TERM_AUX_ACTION:
+			case EVSEL__CONFIG_TERM_USR_CHG_CONFIG:
+			case EVSEL__CONFIG_TERM_USR_CHG_CONFIG1:
+			case EVSEL__CONFIG_TERM_USR_CHG_CONFIG2:
+			case EVSEL__CONFIG_TERM_USR_CHG_CONFIG3:
+			case EVSEL__CONFIG_TERM_USR_CHG_CONFIG4:
+			case EVSEL__CONFIG_TERM_RATIO_TO_PREV:
+			default:
+				new_term->val.val = val;
+				break;
+			}
 		}
 	}
 	return 0;
-- 
2.53.0


             reply	other threads:[~2026-02-12 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 12:53 Thomas Richter [this message]
2026-02-12 18:17 ` [PATCH linux-next] perf parse-events: Fix big-endian 'overwrite' by writing correct union member Ian Rogers
2026-02-16 10:04   ` Thomas Richter
2026-02-16 11:18     ` James Clark
2026-02-16 11:34       ` James Clark

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=20260212125315.777356-1-tmricht@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=japo@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sumanthk@linux.ibm.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