[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240215213916.385127578@goodmis.org>
Date: Thu, 15 Feb 2024 16:39:16 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-linus][PATCH 0/4] tracing: More fixes for v6.8
More fixes for 6.8
- Fix a false positive kmemleak on saved cmdlines
Now that the saved_cmdlines structure is allocated via alloc_page()
and not via kmalloc() it has become invisible to kmemleak.
The allocation done to one of its pointers was flagged as a
dangling allocation leak. Make kmemleak aware of this allocation
and free.
- Fix synthetic event dynamic strings.
A update that cleaned up the synthetic event code removed the
return value of trace_string(), and had it return zero instead
of the length, causing dynamic strings in the synthetic event
to always have zero size.
- Clean up documentation and header files for seq_buf
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: 6efe4d18796934b8ada66c1c446510e7f2d9b972
Andy Shevchenko (2):
seq_buf: Don't use "proxy" headers
seq_buf: Fix kernel documentation
Steven Rostedt (Google) (1):
tracing: Inform kmemleak of saved_cmdlines allocation
Thorsten Blum (1):
tracing/synthetic: Fix trace_string() return value
----
include/linux/seq_buf.h | 17 ++++++++------
kernel/trace/trace.c | 3 +++
kernel/trace/trace_events_synth.c | 3 ++-
lib/seq_buf.c | 49 ++++++++++++++++++++++++---------------
4 files changed, 45 insertions(+), 27 deletions(-)
Powered by blists - more mailing lists