public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/4] tracing: Fixes for v6.19
Date: Thu, 18 Dec 2025 08:55:04 -0500	[thread overview]
Message-ID: <20251218135504.301981830@kernel.org> (raw)

tracing fixes for v6.19:

- Add Documentation/core-api/tracepoint.rst to TRACING in MAINTAINERS file

  Updates to the tracepoint.rst document should be reviewed by the
  tracing maintainers.

- Fix warning triggered by perf attaching to synthetic events

  The synthetic events do not add a function to be registered when
  perf attaches to them. This causes a warning when perf registers
  a synthetic event and passes a NULL pointer to the tracepoint register
  function. Ideally synthetic events should be updated to work with
  perf, but as that's a feature and not a bug fix, simply now return
  -ENODEV when perf tries to register an event that has a NULL pointer
  for its function. This no longer causes a kernel warning and simply
  causes the perf code to fail with an error message.

- Fix 32bit overflow in option flag test

  The option's flags changed from 32 bits in size to 64 bits in size.
  Fix one of the places that shift 1 by the option bit number to
  to be 1ULL.

- Fix the output of printing the direct jmp functions

  The enabled_functions that shows how functions are being attached by
  ftrace wasn't updated to accommodate the new direct jmp trampolines
  that set the LSB of the pointer, and outputs garbage. Update the
  output to handle the direct jmp trampolines.

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes

Head SHA1: 39263f986da55c5b7bc328c757fe378a6a41799d


Darrick J. Wong (1):
      tracing: Fix UBSAN warning in __remove_instance()

Lukas Bulwahn (1):
      MAINTAINERS: add tracepoint core-api doc files to TRACING

Menglong Dong (1):
      ftrace: Fix address for jmp mode in t_show()

Steven Rostedt (1):
      tracing: Do not register unsupported perf events

----
 MAINTAINERS                 | 1 +
 kernel/trace/ftrace.c       | 7 +++++--
 kernel/trace/trace.c        | 2 +-
 kernel/trace/trace_events.c | 2 ++
 4 files changed, 9 insertions(+), 3 deletions(-)

             reply	other threads:[~2025-12-18 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 13:55 Steven Rostedt [this message]
2025-12-18 13:55 ` [for-linus][PATCH 1/4] MAINTAINERS: add tracepoint core-api doc files to TRACING Steven Rostedt
2025-12-18 13:55 ` [for-linus][PATCH 2/4] tracing: Do not register unsupported perf events Steven Rostedt
2025-12-18 13:55 ` [for-linus][PATCH 3/4] tracing: Fix UBSAN warning in __remove_instance() Steven Rostedt
2025-12-18 13:55 ` [for-linus][PATCH 4/4] ftrace: Fix address for jmp mode in t_show() Steven Rostedt

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=20251218135504.301981830@kernel.org \
    --to=rostedt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    /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