From: Steven Rostedt <rostedt@goodmis.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/4] tracing: More fixes for v6.8
Date: Thu, 15 Feb 2024 16:39:16 -0500 [thread overview]
Message-ID: <20240215213916.385127578@goodmis.org> (raw)
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(-)
next reply other threads:[~2024-02-15 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 21:39 Steven Rostedt [this message]
2024-02-15 21:39 ` [for-linus][PATCH 1/4] tracing: Inform kmemleak of saved_cmdlines allocation Steven Rostedt
2024-02-15 21:39 ` [for-linus][PATCH 2/4] tracing/synthetic: Fix trace_string() return value Steven Rostedt
2024-02-15 21:39 ` [for-linus][PATCH 3/4] seq_buf: Dont use "proxy" headers Steven Rostedt
2024-02-15 21:39 ` [for-linus][PATCH 4/4] seq_buf: Fix kernel documentation 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=20240215213916.385127578@goodmis.org \
--to=rostedt@goodmis.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