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/5] ring-buffer: Fixes for v6.14
Date: Fri, 14 Feb 2025 22:52:31 -0500 [thread overview]
Message-ID: <20250215035231.786853904@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ring-buffer/fixes
Head SHA1: b9b289edd70d130f489317bbd04c2103053a77e3
Steven Rostedt (5):
ring-buffer: Unlock resize on mmap error
tracing: Have the error of __tracing_resize_ring_buffer() passed to user
ring-buffer: Validate the persistent meta data subbuf array
tracing: Do not allow mmap() of persistent ring buffer
ring-buffer: Update pages_touched to reflect persistent buffer content
----
kernel/trace/ring_buffer.c | 28 ++++++++++++++++++++++++++--
kernel/trace/trace.c | 12 +++++-------
2 files changed, 31 insertions(+), 9 deletions(-)
next reply other threads:[~2025-02-15 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 3:52 Steven Rostedt [this message]
2025-02-15 3:52 ` [for-linus][PATCH 1/5] ring-buffer: Unlock resize on mmap error Steven Rostedt
2025-02-15 3:52 ` [for-linus][PATCH 2/5] tracing: Have the error of __tracing_resize_ring_buffer() passed to user Steven Rostedt
2025-02-15 3:52 ` [for-linus][PATCH 3/5] ring-buffer: Validate the persistent meta data subbuf array Steven Rostedt
2025-02-15 3:52 ` [for-linus][PATCH 4/5] tracing: Do not allow mmap() of persistent ring buffer Steven Rostedt
2025-02-15 3:52 ` [for-linus][PATCH 5/5] ring-buffer: Update pages_touched to reflect persistent buffer content 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=20250215035231.786853904@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 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.