Commit b83a8ff87a0c for kernel

commit b83a8ff87a0c10c1d86eb7f96e14009d91fae024
Merge: 102606402f4f 361eb853c655
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 24 17:18:57 2026 -0800

    Merge tag 'trace-v6.19-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace

    Pull tracing fixes from Steven Rostedt:

     - 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 stacktrace.

     - 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.

    * tag 'trace-v6.19-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
      scripts/tracepoint-update: Fix memory leak in add_string() on failure
      function_graph: Fix args pointer mismatch in print_graph_retval()
      tracing: Avoid possible signed 64-bit truncation
      tracing: Fix crash on synthetic stacktrace field usage