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-next][PATCH 00/13] tracing: Reading user space data in syscall events for v6.19
Date: Wed, 29 Oct 2025 10:40:41 -0400 [thread overview]
Message-ID: <20251029144041.475297995@kernel.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: 25bd47a592751eba6ed337e6293dc69f8aa2452f
Steven Rostedt (13):
tracing: Make trace_user_fault_read() exposed to rest of tracing
tracing: Have syscall trace events read user space string
perf: tracing: Simplify perf_sysenter_enable/disable() with guards
perf: tracing: Have perf system calls read user space
tracing: Have system call events record user array data
tracing: Display some syscall arrays as strings
tracing: Allow syscall trace events to read more than one user parameter
tracing: Add a config and syscall_user_buf_size file to limit amount written
tracing: Show printable characters in syscall arrays
tracing: Add trace_seq_pop() and seq_buf_pop()
tracing: Add parsing of flags to the sys_enter_openat trace event
tracing: Check for printable characters when printing field dyn strings
tracing: Have persistent ring buffer print syscalls normally
----
Documentation/trace/ftrace.rst | 8 +
include/linux/seq_buf.h | 17 +
include/linux/trace_seq.h | 13 +
include/trace/syscall.h | 8 +-
kernel/trace/Kconfig | 14 +
kernel/trace/trace.c | 327 ++++++++++++---
kernel/trace/trace.h | 20 +
kernel/trace/trace_output.c | 27 +-
kernel/trace/trace_syscalls.c | 929 ++++++++++++++++++++++++++++++++++++++---
9 files changed, 1244 insertions(+), 119 deletions(-)
next reply other threads:[~2025-10-29 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 14:40 Steven Rostedt [this message]
2025-10-29 14:40 ` [for-next][PATCH 01/13] tracing: Make trace_user_fault_read() exposed to rest of tracing Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 02/13] tracing: Have syscall trace events read user space string Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 03/13] perf: tracing: Simplify perf_sysenter_enable/disable() with guards Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 04/13] perf: tracing: Have perf system calls read user space Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 05/13] tracing: Have system call events record user array data Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 06/13] tracing: Display some syscall arrays as strings Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 07/13] tracing: Allow syscall trace events to read more than one user parameter Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 08/13] tracing: Add a config and syscall_user_buf_size file to limit amount written Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 09/13] tracing: Show printable characters in syscall arrays Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 10/13] tracing: Add trace_seq_pop() and seq_buf_pop() Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 11/13] tracing: Add parsing of flags to the sys_enter_openat trace event Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 12/13] tracing: Check for printable characters when printing field dyn strings Steven Rostedt
2025-10-29 14:40 ` [for-next][PATCH 13/13] tracing: Have persistent ring buffer print syscalls normally 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=20251029144041.475297995@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