From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexandre Ghiti <alex@ghiti.fr>, ChenMiao <chenmiao.ku@gmail.com>,
linux-arch@vger.kernel.org
Subject: Re: [RFC][PATCH] ftrace: Make DYNAMIC_FTRACE always enabled for architectures that support it
Date: Thu, 3 Jul 2025 15:52:42 -0400 [thread overview]
Message-ID: <20250703155242.0475137c@gandalf.local.home> (raw)
In-Reply-To: <20250703154916.48e3ada7@gandalf.local.home>
On Thu, 3 Jul 2025 15:49:16 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> diff --git a/include/linux/unwind_deferred.h b/include/linux/unwind_deferred.h
> index 515d2995672d..14efd8c027aa 100644
> --- a/include/linux/unwind_deferred.h
> +++ b/include/linux/unwind_deferred.h
> @@ -28,8 +28,8 @@ void unwind_deferred_cancel(struct unwind_work *work);
>
> static __always_inline void unwind_reset_info(void)
> {
> - if (unlikely(current->unwind_info.id))
> - current->unwind_info.id = 0;
> + if (unlikely(current->unwind_info.id.id))
> + current->unwind_info.id.id = 0;
> /*
> * As unwind_user_faultable() can be called directly and
> * depends on nr_entries being cleared on exit to user,
Bah, I did this while fixing the unwind patches.
Oops!
-- Steve
next prev parent reply other threads:[~2025-07-03 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 15:52 [RFC][PATCH] ftrace: Make DYNAMIC_FTRACE always enabled for architectures that support it Steven Rostedt
2025-07-03 16:57 ` Linus Torvalds
2025-07-03 19:26 ` Steven Rostedt
2025-07-03 19:49 ` Steven Rostedt
2025-07-03 19:52 ` Steven Rostedt [this message]
2025-07-03 20:58 ` Linus Torvalds
2025-07-04 15:12 ` 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=20250703155242.0475137c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alex@ghiti.fr \
--cc=chenmiao.ku@gmail.com \
--cc=linux-arch@vger.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=torvalds@linux-foundation.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