All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Hui Su" <sh_def@163.com>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Fix crash passing ERR_PTR to kthread_stop()
Date: Mon, 17 Aug 2026 12:15:32 +0000	[thread overview]
Message-ID: <20260817121532.9C14A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260817120642.668375-3-sh_def@163.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Using `WARN_ON` inside `event_test_stuff()` causes a massive warning storm and potential soft lockup if kthread creation repeatedly fails.
--

--- Patch [1]: [PATCH v2] tracing: Fix crash passing ERR_PTR to kthread_stop() ---
commit 692df106ab8d8e56701ad9c14c135871ee02df4a
Author: Hui Su <sh_def@163.com>

tracing: Fix crash passing ERR_PTR to kthread_stop()

This commit adds a check for the return value of kthread_run() in
event_test_stuff() to prevent passing an ERR_PTR to kthread_stop() if thread
creation fails under memory pressure during boot-time trace self tests.

> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 0356cae0cf74e..9e941e5805f5e 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -3866,6 +3866,8 @@ static __init void event_test_stuff(void)
>  	struct task_struct *test_thread;
>  
>  	test_thread = kthread_run(event_test_thread, NULL, "test-events");
> +	if (WARN_ON(IS_ERR(test_thread)))
> +		return;

[Severity: High]
Does this risk causing a console flood and soft lockup if thread creation
persistently fails?

During boot-time trace self tests, event_test_stuff() is called within
large loops spanning all trace events:

kernel/trace/trace_events.c:event_trace_self_tests() {
    ...
	list_for_each_entry(file, &tr->events, list) {
        ...
		ftrace_event_enable_disable(file, 1);
		event_test_stuff();
		ftrace_event_enable_disable(file, 0);
    ...
}

If kthread creation fails, WARN_ON prints a full stack trace and returns.
Since event_test_stuff() returns void, the caller blindly continues to the
next trace event, potentially leading to thousands of consecutive stack
dumps.

Could this be changed to WARN_ON_ONCE() or modified to abort the test loop
gracefully?

>  	msleep(1);
>  	kthread_stop(test_thread);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260817120642.668375-3-sh_def@163.com?part=1

  reply	other threads:[~2026-08-17 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 12:06 [PATCH v2] tracing: Fix crash passing ERR_PTR to kthread_stop() Hui Su
2026-08-17 12:15 ` sashiko-bot [this message]
2026-08-17 13:26   ` 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=20260817121532.9C14A1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sh_def@163.com \
    /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.