From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/3] tracing: A few fixes for 6.5
Date: Wed, 05 Jul 2023 10:40:31 -0400 [thread overview]
Message-ID: <20230705144031.702796304@goodmis.org> (raw)
Tracing fixes for 6.5:
- Fix bad git merge of #endif in arm64 code
A merge of the arm64 tree caused #endif to go into the wrong place
- Fix crash on lseek of write access to tracefs/error_log
Opening error_log as write only, and then doing an lseek() causes
a kernel panic, because the lseek() handle expects a "seq_file"
to exist (which is not done on write only opens). Use tracing_lseek()
that tests for this instead of calling the default seq lseek handler.
- Check for negative instead of -E2BIG for error on strscpy() returns
Instead of testing for -E2BIG from strscpy(), to be more robust,
check for less than zero, which will make sure it catches any error
that strscpy() may someday return.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/core
Head SHA1: fddca7db4a4c17f7333793dfb5308d80c76d2896
Arnd Bergmann (1):
arm64: ftrace: fix build error with CONFIG_FUNCTION_GRAPH_TRACER=n
Mateusz Stachyra (1):
tracing: Fix null pointer dereference in tracing_err_log_open()
Steven Rostedt (Google) (1):
tracing/boot: Test strscpy() against less than zero for error
----
arch/arm64/kernel/asm-offsets.c | 2 +-
kernel/trace/trace.c | 2 +-
kernel/trace/trace_boot.c | 8 ++++----
3 files changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2023-07-05 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:40 Steven Rostedt [this message]
2023-07-05 14:40 ` [for-linus][PATCH 1/3] tracing: Fix null pointer dereference in tracing_err_log_open() Steven Rostedt
2023-07-05 14:40 ` [for-linus][PATCH 2/3] arm64: ftrace: fix build error with CONFIG_FUNCTION_GRAPH_TRACER=n Steven Rostedt
2023-07-05 14:40 ` [for-linus][PATCH 3/3] tracing/boot: Test strscpy() against less than zero for error 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=20230705144031.702796304@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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