public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vishal Chourasia <vishalc@linux.ibm.com>
To: Ethan Tidmore <ethantidmore06@gmail.com>
Cc: tglx@kernel.org, peterz@infradead.org, mpe@ellerman.id.au,
	cai@lca.pw, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/core: Fix error pointer dereference
Date: Thu, 26 Feb 2026 10:48:28 +0530	[thread overview]
Message-ID: <aZ_XpPCx474J9qIz@linux.ibm.com> (raw)
In-Reply-To: <20260217180633.524129-1-ethantidmore06@gmail.com>

On Tue, Feb 17, 2026 at 12:06:33PM -0600, Ethan Tidmore wrote:
> The function idle_thread_get() can return an error pointer and is not
> checked for one. Add check for error pointer.
> 
> Detected by Smatch:
> kernel/cpu.c:911 finish_cpu() error:
> 'idle' dereferencing possible ERR_PTR()
> 
> Fixes: bf2c59fce4074 ("sched/core: Fix illegal RCU from offline CPUs")
> Signed-off-by: Ethan Tidmore <ethantidmore06@gmail.com>
> ---
>  kernel/cpu.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index bc4f7a9ba64e..30af888d1bc1 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -908,7 +908,12 @@ static int bringup_cpu(unsigned int cpu)
>  static int finish_cpu(unsigned int cpu)
>  {
>  	struct task_struct *idle = idle_thread_get(cpu);
> -	struct mm_struct *mm = idle->active_mm;
> +	struct mm_struct *mm;
> +
> +	if (IS_ERR(idle))
> +		return PTR_ERR(idle);
> +
> +	mm = idle->active_mm;
>  
>  	/*
>  	 * sched_force_init_mm() ensured the use of &init_mm,
> -- 
> 2.53.0
> 
Reviewed-by: Vishal Chourasia <vishalc@linux.ibm.com>

      parent reply	other threads:[~2026-02-26  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 18:06 [PATCH] sched/core: Fix error pointer dereference Ethan Tidmore
2026-02-20 10:20 ` Peter Zijlstra
2026-02-20 14:19   ` Ethan Tidmore
2026-02-26  5:18 ` Vishal Chourasia [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=aZ_XpPCx474J9qIz@linux.ibm.com \
    --to=vishalc@linux.ibm.com \
    --cc=cai@lca.pw \
    --cc=ethantidmore06@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=peterz@infradead.org \
    --cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox