All of lore.kernel.org
 help / color / mirror / Atom feed
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] fgraph: Fixes for 6.12
Date: Fri, 25 Oct 2024 06:19:10 -0400	[thread overview]
Message-ID: <20241025101910.054222333@goodmis.org> (raw)


Fixes for function graph:

- Fix missing mutex unlock in error path of register_ftrace_graph()

  A previous fix added a return on an error path and forgot to unlock the
  mutex. Instead of dealing with error paths, use guard(mutex) as the mutex
  is just released at the exit of the function anyway. Other functions
  in this file should be updated with this, but that's a cleanup and not
  a fix.

- Change cpuhp setup name to be consistent with other cpuhp states

  The same fix that the above patch fixes added a cpuhp_setup_state() call
  with the name of "fgraph_idle_init". I was informed that it should instead
  be something like: "fgraph:online". Update that too.

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ftrace/fixes

Head SHA1: a574e7f80e86c740e241c762923f50077b2c2a30


Li Huafei (1):
      fgraph: Fix missing unlock in register_ftrace_graph()

Steven Rostedt (1):
      fgraph: Change the name of cpuhp state to "fgraph:online"

----
 kernel/trace/fgraph.c | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

             reply	other threads:[~2024-10-25 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 10:19 Steven Rostedt [this message]
2024-10-25 10:19 ` [for-linus][PATCH 1/2] fgraph: Fix missing unlock in register_ftrace_graph() Steven Rostedt
2024-10-25 10:19 ` [for-linus][PATCH 2/2] fgraph: Change the name of cpuhp state to "fgraph:online" 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=20241025101910.054222333@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.