From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4513C223DC6 for ; Sat, 24 Jan 2026 16:47:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769273224; cv=none; b=a9Sn0gRLOFQZfYW6OVqnKVVGL2jD8sFiAPIygja++w8I//went44XKgamCqGaFzMF9isjO6EPg3WkeEboN/wstPigAyFsA73Iae0MPVcWv1SZbq7aKky9P+JZcGZyfhxplNumZ2b/KuyWjDYMyvjYb4dueusFwSbMmrsIkGIZZI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769273224; c=relaxed/simple; bh=tZRp5XrKoZgI8jMPPHtx39TO8AH5jeb/BQlQwxtoxdA=; h=Message-ID:Date:From:To:Cc:Subject; b=jPHL+l2HnrOhlCEdUNkTJnn3oqr9GQtMqjzV/HXggTL2xF5X33U1ilsS5rvhJWighzGNXE72nyVKiopFqgcUFGsfUA1dL1p6ajd+Ed7CXHhJQH7Ow/hY3DteJVMtzN9i0Gi9zpcsRzgPWDj9uXqoOrMk2TjT+Q3JXXoGlRPcJLs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=AAzvrgGT; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="AAzvrgGT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C388BC116D0; Sat, 24 Jan 2026 16:47:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769273223; bh=tZRp5XrKoZgI8jMPPHtx39TO8AH5jeb/BQlQwxtoxdA=; h=Date:From:To:Cc:Subject:From; b=AAzvrgGT0yDNB/jfQViDWr1DKiheTUMtO9z3NSHNcphM9ft73Ejma5xdEUReDbs0j k+06ct19jgn4w8q5Dtb/O8gBupBtDpI4MTC3w1u6kbd8nsx7pVoEPMnX13g+VBh+0j Xya73MRag2JjXn6LpvaGkdxjDCmyfn9Al8tiT9k5LQdiJEwDbeTBK7qRPnDvu5LQMA qStrXPbJJZ2uTv/mV2VPiprwr9mru1szYSYQHwcy7IMrZAPW6K9CAmMLVnKRolWpMu e74kylUidWBRobvEQYlbCWjFtBayvQtTQfsAfgABoHrSsJKwwZ/ceqjDZL+VRilZxB kz08BMfAxbysw== Received: from rostedt by gandalf with local (Exim 4.99.1) (envelope-from ) id 1vjgnO-00000003CmN-2mEF; Sat, 24 Jan 2026 11:47:34 -0500 Message-ID: <20260124162943.928691049@kernel.org> User-Agent: quilt/0.68 Date: Sat, 24 Jan 2026 11:29:43 -0500 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Masami Hiramatsu , Mark Rutland , Mathieu Desnoyers , Andrew Morton Subject: [for-linus][PATCH 0/4] tracing: One crash fix and 3 minor fixes for v6.19 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: tracing fixes for v6.19: - Fix a crash with passing a stacktrace between synthetic events A synthetic event is an event that combines two events into a single event that can display fields from both events as well as the time delta that took place between the events. It can also pass a stacktrace from the first event so that it can be displayed by the synthetic event (this is useful to get a stacktrace of a task scheduling out when blocked and recording the time it was blocked for). A synthetic event can also connect an existing synthetic event to another event. An issue was found that if the first synthetic event had a stacktrace as one of its fields, and that stacktrace field was passed to the new synthetic event to be displayed, it would crash the kernel. This was due to the stacktrace not being saved as a stacktrace but was still marked as one. When the stacktrace was read, it would try to read an array but instead read the integer metadata of the stacktrace and dereferenced a bad value. Fix this by saving the stacktrace field as a stracktrace. - Fix possible overflow in cmp_mod_entry() compare function A binary search is used to find a module address and if the addresses are greater than 2GB apart it could lead to truncation and cause a bad search result. Use normal compares instead of a subtraction between addresses to calculate the compare value. - Fix output of entry arguments in function graph tracer Depending on the configurations enabled, the entry can be two different types that hold the argument array. The macro FGRAPH_ENTRY_ARGS() is used to find the correct arguments from the given type. One location was missed and still referenced the arguments directly via entry->args and could produce the wrong value depending on how the kernel was configured. - Fix memory leak in scripts/tracepoint-update build tool If the array fails to allocate, the memory for the values needs to be freed and was not. Free the allocated values if the array failed to allocate. git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git trace/fixes Head SHA1: 361eb853c655288f3b5c8020f6cd95d69ffe6479 Donglin Peng (1): function_graph: Fix args pointer mismatch in print_graph_retval() Ian Rogers (1): tracing: Avoid possible signed 64-bit truncation Steven Rostedt (1): tracing: Fix crash on synthetic stacktrace field usage Weigang He (1): scripts/tracepoint-update: Fix memory leak in add_string() on failure ---- kernel/trace/trace.c | 8 ++++---- kernel/trace/trace_events_hist.c | 9 +++++++++ kernel/trace/trace_events_synth.c | 8 +++++++- kernel/trace/trace_functions_graph.c | 2 +- scripts/tracepoint-update.c | 2 ++ 5 files changed, 23 insertions(+), 6 deletions(-)