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.17
Date: Sat, 06 Sep 2025 18:17:51 -0400	[thread overview]
Message-ID: <20250906221751.054623340@kernel.org> (raw)

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

Head SHA1: c1628c00c4351dd0727ef7f670694f68d9e663d8


Guenter Roeck (1):
      trace/fgraph: Fix error handling

Luo Gengkun (1):
      tracing: Fix tracing_marker may trigger page fault during preempt_disable

Qianfeng Rong (1):
      trace: Remove redundant __GFP_NOWARN

Vladimir Riabchun (1):
      ftrace/samples: Fix function size computation

Wang Liang (1):
      tracing/osnoise: Fix null-ptr-deref in bitmap_parselist()

----
 kernel/trace/fgraph.c                 | 3 ++-
 kernel/trace/trace.c                  | 4 ++--
 kernel/trace/trace_events_user.c      | 2 +-
 kernel/trace/trace_osnoise.c          | 3 +++
 samples/ftrace/ftrace-direct-modify.c | 2 +-
 5 files changed, 9 insertions(+), 5 deletions(-)

             reply	other threads:[~2025-09-06 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-06 22:17 Steven Rostedt [this message]
2025-09-06 22:17 ` [for-linus][PATCH 1/5] trace: Remove redundant __GFP_NOWARN Steven Rostedt
2025-09-06 22:17 ` [for-linus][PATCH 2/5] tracing: Fix tracing_marker may trigger page fault during preempt_disable Steven Rostedt
2025-09-06 22:17 ` [for-linus][PATCH 3/5] ftrace/samples: Fix function size computation Steven Rostedt
2025-09-06 22:17 ` [for-linus][PATCH 4/5] trace/fgraph: Fix error handling Steven Rostedt
2025-09-06 22:17 ` [for-linus][PATCH 5/5] tracing/osnoise: Fix null-ptr-deref in bitmap_parselist() 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=20250906221751.054623340@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.