From: Mark Rutland <mark.rutland@arm.com>
To: Koichiro Den <koichiro.den@canonical.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vmstat: disable vmstat_work on vmstat_cpu_down_prep()
Date: Mon, 6 Jan 2025 10:04:43 +0000 [thread overview]
Message-ID: <Z3uqu0ue0agUASzz@J2N7QTR9R3> (raw)
In-Reply-To: <2q7ge6cgzeowqffyn6w6ed4trhaaumv5ubdgud2tsoolen7wpw@4akuomhbacyh>
On Sat, Jan 04, 2025 at 01:00:17PM +0900, Koichiro Den wrote:
> On Fri, Jan 03, 2025 at 11:33:19PM +0000, Lorenzo Stoakes wrote:
> > Hi,
> >
> > I observed a warning in my qemu and real hardware, which I bisected to this commit:
> >
> > [ 0.087733] ------------[ cut here ]------------
> > [ 0.087733] workqueue: work disable count underflowed
> > [ 0.087733] WARNING: CPU: 1 PID: 21 at kernel/workqueue.c:4313 enable_work+0xb5/0xc0
FWIW, I hit similar when testing v6.13-rc6 defconfig on arm64, when
booting secondaries I always get a splat (trimmed):
| ------------[ cut here ]------------
| workqueue: work disable count underflowed
| WARNING: CPU: 1 PID: 21 at kernel/workqueue.c:4317 enable_work+0xfc/0x108
| Modules linked in:
| CPU: 1 UID: 0 PID: 21 Comm: cpuhp/1 Not tainted 6.13.0-rc6 #1
| Hardware name: linux,dummy-virt (DT)
| [...]
| Call trace:
| enable_work+0xfc/0x108 (P)
| enable_delayed_work+0x10/0x1c
| vmstat_cpu_online+0x88/0xbc
| cpuhp_invoke_callback+0x10c/0x208
| cpuhp_thread_fun+0xb0/0x1a0
| smpboot_thread_fn+0x20c/0x234
| kthread+0x110/0x114
| ret_from_fork+0x10/0x20
| ---[ end trace 0000000000000000 ]---
[...]
> In my current view, the simplest solution would be to make sure a local
> vmstat_work is disabled until vmstat_cpu_online() runs for the cpu, even
> during boot-up. The following patch suppresses the warning:
>
> diff --git a/mm/vmstat.c b/mm/vmstat.c
> index 0889b75cef14..19ceed5d34bf 100644
> --- a/mm/vmstat.c
> +++ b/mm/vmstat.c
> @@ -2122,10 +2122,14 @@ static void __init start_shepherd_timer(void)
> {
> int cpu;
>
> - for_each_possible_cpu(cpu)
> + for_each_possible_cpu(cpu) {
> INIT_DEFERRABLE_WORK(per_cpu_ptr(&vmstat_work, cpu),
> vmstat_update);
>
> + /* will be enabled on vmstat_cpu_online */
> + disable_delayed_work_sync(&per_cpu(vmstat_work, cpu));
> + }
> +
> schedule_delayed_work(&shepherd,
> round_jiffies_relative(sysctl_stat_interval));
> }
FWIW, the above solves the warning for me.
Mark.
next prev parent reply other threads:[~2025-01-06 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 3:33 Koichiro Den
2025-01-03 23:33 ` Lorenzo Stoakes
2025-01-04 4:00 ` Koichiro Den
2025-01-06 2:18 ` Charalampos Mitrodimas
2025-01-06 10:04 ` Mark Rutland [this message]
2025-01-06 10:18 ` Geert Uytterhoeven
2025-01-06 10:52 ` Lorenzo Stoakes
2025-01-06 12:53 ` Charalampos Mitrodimas
2025-01-06 12:58 ` Lorenzo Stoakes
2025-01-06 13:03 ` Koichiro Den
2025-01-06 13:53 ` Koichiro Den
2025-01-07 1:18 ` [PATCH] Simple fix Huacai Chen
2025-01-07 3:35 ` Matthew Wilcox
2025-01-07 3:58 ` Huacai Chen
2025-01-07 8:47 ` Lorenzo Stoakes
2025-01-07 10:29 ` Huacai Chen
2025-01-07 11:00 ` Lorenzo Stoakes
2025-01-08 2:22 ` Koichiro Den
2025-01-08 2:26 ` Koichiro Den
2025-01-08 2:31 ` Huacai Chen
2025-01-08 3:41 ` Koichiro Den
2025-01-08 3:57 ` 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=Z3uqu0ue0agUASzz@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=koichiro.den@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.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