mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Fwd: kernel/cpu.c: linux misses the initialization of one CPU (off-by-one regression)
@ 2023-05-29  1:50 Bagas Sanjaya
  2023-06-20 12:36 ` Linux regression tracking #update (Thorsten Leemhuis)
  0 siblings, 1 reply; 2+ messages in thread
From: Bagas Sanjaya @ 2023-05-29  1:50 UTC (permalink / raw)
  To: Linux Kernel Mailing List, Linux Regressions, Linux x86
  Cc: David Woodhouse, Thomas Gleixner, Peter Zijlstra (Intel),
	Michael Kelley, Oleksandr Natalenko, Helge Deller,
	Guilherme G. Piccoli, Vincent Donnefort, Bert Karwatzki

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> Since commit 18415f33e2ac4ab382cbca8b5ff82a9036b5bd49 linux misses the initialization of 1 CPU when the CONFIG_NR_CPUS is equal to the actual number of CPUs in the system. One can work around the issue by increasing CONFIG_NR_CPUS or apply the following patch:
> 
> From aa5ef661936655f0d806fdbf2d28fc9513dd5c69 Mon Sep 17 00:00:00 2001
> From: Bert Karwatzki <spasswolf@web.de>
> Date: Sun, 28 May 2023 14:35:45 +0200
> Subject: [PATCH] Fix CPU detection when CONFIG_NR_CPUS is equal to the actual
>  number of CPUs.
> 
> Signed-off-by: Bert Karwatzki <spasswolf@web.de>
> ---
>  kernel/cpu.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index 005f863a3d2b..5e900b531827 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -1770,7 +1770,7 @@ static void __init cpuhp_bringup_mask(const struct cpumask *mask, unsigned int n
>  	for_each_cpu(cpu, mask) {
>  		struct cpuhp_cpu_state *st = per_cpu_ptr(&cpuhp_state, cpu);
>  
> -		if (!--ncpus)
> +		if (!ncpus--)
>  			break;
>  
>  		if (cpu_up(cpu, target) && can_rollback_cpu(st)) {
> -- 
> 2.40.1

Anyway, I'm adding it to regzbot:

#regzbot introduced: 18415f33e2ac4a https://bugzilla.kernel.org/show_bug.cgi?id=217498
#regzbot title: Off-by-one CPU initalization when CONFIG_NR_CPUS equal to actual system CPU count

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217498

-- 
An old man doll... just what I always wanted! - Clara

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Fwd: kernel/cpu.c: linux misses the initialization of one CPU (off-by-one regression)
  2023-05-29  1:50 Fwd: kernel/cpu.c: linux misses the initialization of one CPU (off-by-one regression) Bagas Sanjaya
@ 2023-06-20 12:36 ` Linux regression tracking #update (Thorsten Leemhuis)
  0 siblings, 0 replies; 2+ messages in thread
From: Linux regression tracking #update (Thorsten Leemhuis) @ 2023-06-20 12:36 UTC (permalink / raw)
  To: Bagas Sanjaya, Linux Kernel Mailing List, Linux Regressions, Linux x86
  Cc: David Woodhouse, Thomas Gleixner, Peter Zijlstra (Intel),
	Michael Kelley, Oleksandr Natalenko, Helge Deller,
	Guilherme G. Piccoli, Vincent Donnefort, Bert Karwatzki

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 29.05.23 03:50, Bagas Sanjaya wrote:

> I notice a regression report on Bugzilla [1]. Quoting from it:
> [...]
> #regzbot introduced: 18415f33e2ac4a https://bugzilla.kernel.org/show_bug.cgi?id=217498
> #regzbot title: Off-by-one CPU initalization when CONFIG_NR_CPUS equal to actual system CPU count

Fix in next (just like the culprit):

#regzbot fix: 06c6796e0304234
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-06-20 12:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-05-29  1:50 Fwd: kernel/cpu.c: linux misses the initialization of one CPU (off-by-one regression) Bagas Sanjaya
2023-06-20 12:36 ` Linux regression tracking #update (Thorsten Leemhuis)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®