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/3] tracing: Fixes for v7.1
Date: Wed, 29 Apr 2026 16:14:53 -0400	[thread overview]
Message-ID: <20260429201453.449214720@kernel.org> (raw)


tracing fixes for v7.1:

- Fix inverted check of registering the stats for branch tracing

  When calling register_stat_tracer() which returns zero on success and
  negative on error, the callers were checking the return of zero as an
  error and printing a warning message. Because this was just a normal
  printk() message and not a WARN(), it wasn't caught in any testing.

  Fix the check to print the warning message when an error actually happens.

- Fix a typo in a comment in tracepoint.h

- Limit the size of event probes to 3K in size

  It is possible to create a dynamic event probe via the tracefs system that
  is greater than the max size of an event that the ring buffer can hold.
  This basically causes the event to become useless. Limit the size of an
  event probe to be 3K as that should be large enough to handle any dynamic
  events being created, and fits within the PAGE_SIZE sub-buffers of the
  ring buffer.

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

Head SHA1: b2aa3b4d64e460ac606f386c24e7d8a873ce6f1a


Breno Leitao (1):
      tracing: branch: Fix inverted check on stat tracer registration

Sheng Che Peng (1):
      tracepoint: Fix typo in tracepoint.h comment

Steven Rostedt (1):
      tracing/probes: Limit size of event probe to 3K

----
 include/linux/tracepoint.h  | 2 +-
 kernel/trace/trace_branch.c | 8 ++++----
 kernel/trace/trace_probe.c  | 6 ++++++
 kernel/trace/trace_probe.h  | 4 +++-
 4 files changed, 14 insertions(+), 6 deletions(-)

             reply	other threads:[~2026-04-29 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 20:14 Steven Rostedt [this message]
2026-04-29 20:14 ` [for-linus][PATCH 1/3] tracing: branch: Fix inverted check on stat tracer registration Steven Rostedt
2026-04-29 20:14 ` [for-linus][PATCH 2/3] tracepoint: Fix typo in tracepoint.h comment Steven Rostedt
2026-04-29 20:14 ` [for-linus][PATCH 3/3] tracing/probes: Limit size of event probe to 3K 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=20260429201453.449214720@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