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/2] tracing: Two minor fixes for 6.13
Date: Tue, 24 Dec 2024 21:45:36 -0500 [thread overview]
Message-ID: <20241225024536.865653915@goodmis.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Two minor tracing fixes for 6.13:
- Add "const" to "char *" in event structure field that gets assigned
literals.
- Check size of input passed into the tracing cpumask file.
If a too large of an input gets passed into the cpumask file, it could
trigger a warning in the bitmask parsing code.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes
Head SHA1: 98feccbf32cfdde8c722bc4587aaa60ee5ac33f0
Christian Göttsche (1):
tracing: Constify string literal data member in struct trace_event_call
Lizhi Xu (1):
tracing: Prevent bad count for tracing_cpumask_write
----
include/linux/trace_events.h | 2 +-
kernel/trace/trace.c | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
next reply other threads:[~2024-12-25 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 2:45 Steven Rostedt [this message]
2024-12-25 2:45 ` [for-linus][PATCH 1/2] tracing: Constify string literal data member in struct trace_event_call Steven Rostedt
2024-12-25 2:45 ` [for-linus][PATCH 2/2] tracing: Prevent bad count for tracing_cpumask_write 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=20241225024536.865653915@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