The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Leon Hwang <leon.hwang@linux.dev>
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Jiri Olsa <jolsa@kernel.org>, Andrii Nakryiko <andrii@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Leon Hwang <leon.hwang@linux.dev>
Subject: [PATCH 0/4] ftrace: Protect RCU accesses to direct_functions
Date: Thu, 30 Jul 2026 23:04:07 +0800	[thread overview]
Message-ID: <20260730150411.88667-1-leon.hwang@linux.dev> (raw)

Sashiko reported a potential issue of directly accessing
direct_functions [1], which will be addressed by patch #1.

The patch #2 and #3 protect accesses to the RCU-managed direct_functions
hash in its delete, and modify paths.

The final patch removes an unnecessary empty argument from a
scoped_guard() invocation.

[1] https://lore.kernel.org/all/20260727145217.72B9C1F000E9@smtp.kernel.org/

Leon Hwang (4):
  ftrace: Protect direct_functions in ftrace_find_rec_direct
  ftrace: Protect direct_functions in update_ftrace_direct_del
  ftrace: Protect direct_functions in update_ftrace_direct_mod
  ftrace: Drop extra comma in trace_buffered_event_enable

 kernel/trace/ftrace.c | 27 ++++++++++++++++++---------
 kernel/trace/trace.c  |  2 +-
 2 files changed, 19 insertions(+), 10 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-07-30 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 15:04 Leon Hwang [this message]
2026-07-30 15:04 ` [PATCH 1/4] ftrace: Protect direct_functions in ftrace_find_rec_direct Leon Hwang
2026-07-30 15:04 ` [PATCH 2/4] ftrace: Protect direct_functions in update_ftrace_direct_del Leon Hwang
2026-07-30 15:04 ` [PATCH 3/4] ftrace: Protect direct_functions in update_ftrace_direct_mod Leon Hwang
2026-07-30 15:04 ` [PATCH 4/4] ftrace: Drop extra comma in trace_buffered_event_enable Leon Hwang

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=20260730150411.88667-1-leon.hwang@linux.dev \
    --to=leon.hwang@linux.dev \
    --cc=andrii@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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