From: Steven Rostedt <rostedt@goodmis.org>
To: Haotian Zhang <vulab@iscas.ac.cn>
Cc: mhiramat@kernel.org, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] samples/ftrace: Fix kthread_stop() on ERR_PTR in ftrace-direct-multi-modify
Date: Tue, 25 Aug 2026 08:56:07 -0400 [thread overview]
Message-ID: <20260825085607.46c3814e@gandalf.local.home> (raw)
In-Reply-To: <20260825093421.7377-1-vulab@iscas.ac.cn>
On Tue, 25 Aug 2026 17:34:21 +0800
Haotian Zhang <vulab@iscas.ac.cn> wrote:
> ftrace_direct_multi_init() assigns kthread_run()'s return value to
> simple_tsk without an IS_ERR() check. When kthread_run() fails it
> returns ERR_PTR(-ENOMEM), but init still returns 0, so the module loads
> with simple_tsk holding an error pointer. On unload,
> ftrace_direct_multi_exit() then passes that ERR_PTR to kthread_stop(),
> leading to a null-pointer-dereference.
>
> Check the return value of kthread_run() with IS_ERR(); on failure,
> unregister the ftrace direct call and propagate the error code.
>
> Fixes: e1067a07cfbc ("ftrace/samples: Add module to test multi direct modify interface")
> Signed-off-by: Haotian Zhang <vulab@iscas.ac.cn>
> ---
> samples/ftrace/ftrace-direct-multi-modify.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/samples/ftrace/ftrace-direct-multi-modify.c b/samples/ftrace/ftrace-direct-multi-modify.c
> index 8f7986d698d8..f339131654c7 100644
> --- a/samples/ftrace/ftrace-direct-multi-modify.c
> +++ b/samples/ftrace/ftrace-direct-multi-modify.c
> @@ -364,8 +364,13 @@ static int __init ftrace_direct_multi_init(void)
>
> ret = register_ftrace_direct(&direct, my_tramp);
>
> - if (!ret)
> + if (!ret) {
> simple_tsk = kthread_run(simple_thread, NULL, "event-sample-fn");
> + if (IS_ERR(simple_tsk)) {
> + unregister_ftrace_direct(&direct, my_tramp, true);
> + ret = PTR_ERR(simple_tsk);
> + }
> + }
> return ret;
> }
>
And simplify this one too.
Oh, and if you have a series "[PATCH 1/2]" then you need a cover letter and
have each patch be a reply to of that patch. Otherwise just send the
patches as is without the numbered series. Because sending the patches one
by one with a series number makes it confusing.
-- Steve
-- Steve
prev parent reply other threads:[~2026-08-25 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 9:34 [PATCH 1/2] samples/ftrace: Fix kthread_stop() on ERR_PTR in ftrace-direct-multi-modify Haotian Zhang
2026-08-25 12:56 ` Steven Rostedt [this message]
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=20260825085607.46c3814e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=vulab@iscas.ac.cn \
/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