The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Hui Su <sh_def@163.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: Fix crash passing ERR_PTR to kthread_stop()
Date: Sat, 8 Aug 2026 07:17:08 +0900	[thread overview]
Message-ID: <20260808071708.6bcbac3a30c5a58fa1a4c2b0@kernel.org> (raw)
In-Reply-To: <20260807154145.2846521-2-sh_def@163.com>

On Fri,  7 Aug 2026 23:41:46 +0800
Hui Su <sh_def@163.com> wrote:

> In test_ringbuffer()'s out_free cleanup loop, the check
> `!rb_threads[cpu]` only catches NULL entries and misses entries that
> hold an ERR_PTR.
> 
> rb_threads[] is static, so unassigned slots are NULL. But when
> kthread_run_on_cpu() fails for a cpu, it stores ERR_PTR(-ENOMEM) (or
> -EINTR) in rb_threads[cpu] before the creation loop jumps to out_free.
> That entry is non-NULL, so the old `!ptr` check does not break, and the
> cleanup proceeds to call kthread_stop() on the ERR_PTR. kthread_stop()
> then dereferences the bogus pointer, crashing the kernel during the
> late_initcall self-test.
> 
> crash logs:
>   BUG: kernel NULL pointer dereference, address: 000000000000001c
>   Oops: 0002 [#1] SMP NOPTI
>   CPU: 1 PID: 1 Comm: swapper/0 Not tainted 7.2.0-rc6-dirty #7 PREEMPT(lazy)
>   RIP: 0010:kthread_stop+0x2e/0x220
>   RBX: fffffffffffffff4
>   CR2: 000000000000001c
>   Call Trace:
>    <TASK>
>    test_ringbuffer+0x1ec/0x650
>    do_one_initcall+0x6c/0x2c0
>    kernel_init_freeable+0x21d/0x420
>    kernel_init+0x15/0x1c0
>    ret_from_fork+0x21b/0x320
>    </TASK>
>   Kernel panic - not syncing: Fatal exception
> 
> Fixes: 64ed3a049e3e ("ring-buffer: make use of the helper function kthread_run_on_cpu()")
> Signed-off-by: Hui Su <sh_def@163.com>

Look good to me.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Thank you!

> ---
>  kernel/trace/ring_buffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 8e2485bb3aa8..6af7e36ca526 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -8214,7 +8214,7 @@ static __init int test_ringbuffer(void)
>  
>   out_free:
>  	for_each_online_cpu(cpu) {
> -		if (!rb_threads[cpu])
> +		if (IS_ERR_OR_NULL(rb_threads[cpu]))
>  			break;
>  		kthread_stop(rb_threads[cpu]);
>  	}
> -- 
> 2.43.0
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      parent reply	other threads:[~2026-08-07 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 15:41 [PATCH] ring-buffer: Fix crash passing ERR_PTR to kthread_stop() Hui Su
2026-08-07 16:50 ` Vincent Donnefort
2026-08-07 22:17 ` Masami Hiramatsu [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=20260808071708.6bcbac3a30c5a58fa1a4c2b0@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox