All of lore.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/5] tracing: Fixes for v6.19
Date: Thu, 08 Jan 2026 10:51:20 -0500	[thread overview]
Message-ID: <20260108155120.023038025@kernel.org> (raw)


tracing fixes for v6.19:

- Remove useless assignment of soft_mode variable

  The function __ftrace_event_enable_disable() sets "soft_mode" in one of
  the branch paths but doesn't use it after that. Remove the setting of that
  variable.

- Add a cond_resched() in ring_buffer_resize()

  The resize function that allocates all the pages for the ring buffer was
  causing a soft lockup on PREEMPT_NONE configs when allocating large
  buffers on machines with many CPUs. Hopefully this is the last
  cond_resched() needed to be added as PREEMPT_LAZY becomes the norm in the
  future.

- Make ftrace_graph_ent depth field signed

  The "depth" field of struct ftrace_graph_ent was converted from "int" to
  "unsigned long" for alignment reasons to work with being embedded in other
  structures. The conversion from a signed to unsigned caused integrity
  checks to always pass as they were comparing "depth" to less than zero.
  Make the field signed long.

- Add recursion protection to stack trace events

  A infinite recursion was triggered by a stack trace event calling RCU
  which internally called rcu_read_unlock_special(), which triggered an
  event that was also doing stacktraces which cause it to trigger the same
  RCU lock that called rcu_read_unlock_special() again.

  Update the trace_test_and_set_recursion() to add a set of context checks
  for events to use, and have the stack trace event use that for recursion
  protection.

- Make the variable ftrace_dump_on_oops static

  The cleanup of sysctl that moved all the updates to the files that use
  them moved the reference of ftrace_dump_on_oops to where it is used.
  It is no longer used outside of the trace.c file. Make it static.


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

Head SHA1: 1e2ed4bfd50ace3c4272cfab7e9aa90956fb7ae0


Ben Dooks (1):
      trace: ftrace_dump_on_oops[] is not exported, make it static

Julia Lawall (1):
      tracing: Drop unneeded assignment to soft_mode

Steven Rostedt (2):
      ftrace: Make ftrace_graph_ent depth field signed
      tracing: Add recursion protection in kernel stack trace recording

Wupeng Ma (1):
      ring-buffer: Avoid softlockup in ring_buffer_resize() during memory free

----
 include/linux/ftrace.h          | 2 +-
 include/linux/trace_recursion.h | 9 +++++++++
 kernel/trace/ring_buffer.c      | 2 ++
 kernel/trace/trace.c            | 8 +++++++-
 kernel/trace/trace_events.c     | 7 +++----
 5 files changed, 22 insertions(+), 6 deletions(-)

             reply	other threads:[~2026-01-08 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 15:51 Steven Rostedt [this message]
2026-01-08 15:51 ` [for-linus][PATCH 1/5] tracing: Drop unneeded assignment to soft_mode Steven Rostedt
2026-01-08 15:51 ` [for-linus][PATCH 2/5] ring-buffer: Avoid softlockup in ring_buffer_resize() during memory free Steven Rostedt
2026-01-08 15:51 ` [for-linus][PATCH 3/5] ftrace: Make ftrace_graph_ent depth field signed Steven Rostedt
2026-01-08 15:51 ` [for-linus][PATCH 4/5] tracing: Add recursion protection in kernel stack trace recording Steven Rostedt
2026-01-08 15:51 ` [for-linus][PATCH 5/5] trace: ftrace_dump_on_oops[] is not exported, make it static 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=20260108155120.023038025@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.