Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Stefan Wiehler <stefan.wiehler@nokia.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	 Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-mips@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mips: mm: Call rcutree_report_cpu_starting() even earlier
Date: Fri, 10 Apr 2026 14:04:06 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2604101353010.29980@angie.orcam.me.uk> (raw)
In-Reply-To: <20260409164846.3176046-2-stefan.wiehler@nokia.com>

On Thu, 9 Apr 2026, Stefan Wiehler wrote:

> rcutree_report_cpu_starting() must be called on secondary CPUs before
> allocating memory to avoid the following Lockdep-RCU splat when
> CONFIG_PROVE_RCU_LIST=y:
> 
>   WARNING: suspicious RCU usage
>   6.6.119-00d46e15c416-fct #1 Not tainted
>   -----------------------------
>   /kernel/locking/lockdep.c:3762 RCU-list traversed in non-reader section!!

 I have tried to verify your change here, but the warning does not trigger 
with 6.19 as released and CONFIG_SIBYTE_SWARM as the platform (2-way SMP).  

$ grep CONFIG_PROVE_RCU_LIST .config
CONFIG_PROVE_RCU_LIST=y
$ 

Am I missing anything here, anything extra to enable?

> See also commit 55702ec9603e ("mips/smp: Call
> rcutree_report_cpu_starting() earlier").
> 
> Fixes: 231ac951faba ("MIPS: mm: kmalloc tlb_vpn array to avoid stack overflow")

 This does not appear to be a valid commit hash upstream; this is commit 
841ecc979b18 AFAICS.

> diff --git a/arch/mips/kernel/smp.c b/arch/mips/kernel/smp.c
> index 4868e79f3b30..bdb47c70d4f5 100644
> --- a/arch/mips/kernel/smp.c
> +++ b/arch/mips/kernel/smp.c
> @@ -359,8 +359,8 @@ asmlinkage void start_secondary(void)
>  	unsigned int cpu = raw_smp_processor_id();
>  
>  	cpu_probe();
> -	per_cpu_trap_init(false);
>  	rcutree_report_cpu_starting(cpu);
> +	per_cpu_trap_init(false);
>  	mips_clockevent_init();
>  	mp_ops->init_secondary();
>  	cpu_report();

 As I noted in my previous message: is there any reason for cpu_probe() to 
precede this call?

  Maciej

  reply	other threads:[~2026-04-10 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 16:48 [PATCH v2] mips: mm: Call rcutree_report_cpu_starting() even earlier Stefan Wiehler
2026-04-10 13:04 ` Maciej W. Rozycki [this message]
2026-04-13 14:15   ` Stefan Wiehler
2026-04-22 12:16     ` Stefan Wiehler
2026-04-11  8:52 ` Huacai Chen

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=alpine.DEB.2.21.2604101353010.29980@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=stefan.wiehler@nokia.com \
    --cc=tsbogend@alpha.franken.de \
    /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