FAILED: patch "[PATCH] tracing: Have syscall trace events use" failed to apply to 4.19-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 4.19-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 3e2a56e6f639492311e0a8533f0a7aed60816308 Mon Sep 17 00:00:00 2001
From: Steven Rostedt <[email protected]>
Date: Fri, 7 Jan 2022 17:56:56 -0500
Subject: [PATCH] tracing: Have syscall trace events use
trace_event_buffer_lock_reserve()
Currently, the syscall trace events call trace_buffer_lock_reserve() directly, which means that it misses out on some of the filtering optimizations provided by the helper function trace_event_buffer_lock_reserve(). Have the syscall trace events call that instead, as it was missed when adding the update to use the temp buffer when filtering.
kernel/trace/trace_syscalls.c +2 -4
@@ -323,8 +323,7 @@ static void ftrace_syscall_enter(void *data, struct pt_regs *regs, long id) trace_ctx =tracing_gen_ctx (); - buffer = tr->array_buffer.buffer; - event =trace_buffer_lock_reserve (buffer, + event =trace_event_buffer_lock_reserve (&buffer, trace_file, sys_data->enter_event->event.type, size, trace_ctx);if (!event)return ;
@@ -367,8 +366,7 @@ static void ftrace_syscall_exit(void *data, struct pt_regs *regs, long ret) trace_ctx =tracing_gen_ctx (); - buffer = tr->array_buffer.buffer; - event =trace_buffer_lock_reserve (buffer, + event =trace_event_buffer_lock_reserve (&buffer, trace_file, sys_data->exit_event->event.type,sizeof (*entry), trace_ctx);if (!event)