The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	 Omar Sandoval <osandov@osandov.com>, Song Liu <song@kernel.org>,
	 Danielle Costantino <dcostantino@meta.com>,
	kasan-dev@googlegroups.com, kernel-team@meta.com
Subject: Re: [PATCH v2 4/5] workqueue: Show all busy workers in stall diagnostics
Date: Tue, 16 Jun 2026 09:48:03 -0700	[thread overview]
Message-ID: <ajF7pwYm08T6SKbC@gmail.com> (raw)
In-Reply-To: <ajFIIim-Y36KIhRc@pathway.suse.cz>

On Tue, Jun 16, 2026 at 02:57:06PM +0200, Petr Mladek wrote:
> On Tue 2026-06-16 05:44:12, Breno Leitao wrote:
> > Hello Petr,
> > 
> > On Tue, Jun 16, 2026 at 02:38:11PM +0200, Petr Mladek wrote:
> > > On Thu 2026-06-11 07:50:04, Breno Leitao wrote:
> > > >
> > > > Unfortunately I didn't get the other pr_info(), because of console settings,
> > > > but, I can say the following from this issue and previous code:
> > > > 
> > > > 1) in show_cpu_pool_hog, found_running variable is set to false.
> > > > 2) hash_for_each() never found any running task
> > > > 3) The following code was trigger and was very helpful:
> > > > 
> > > >          if (!found_running)
> > > >                 trigger_single_cpu_backtrace(cpu);
> > > 
> > > Great. So, the extra complexity was worth it. Should I clean it and
> > > send a proper patch? Or would you like to do so?
> > 
> > I am happy to do so. I had a chat with tejun yesterday, and I got the
> > impression he is OK with this patch as well.
> 
> Great!
> 
> > > Also I wonder whether it would make sense to revert the commit
> > > 8823eaef45da7f ("workqueue: Show all busy workers in stall
> > > diagnostics").
> > 
> > This patch undo that change already. Would you like to see a full revert
> > or, are you OK with this patch reverting that behaviour? Maybe with
> > a fixes: tag?
> 
> I do not mind how exactly it is done. Reworking the behavior is
> perfectly fine. And the fixes tag would make sense when it was
> not a full revert.

Thanks. I've sent an RFC patchset for us to discuss it there.

https://lore.kernel.org/all/20260616-wq_dump_petr-v1-0-b57473ca6d18@debian.org/

Thanks for your help so far,
--breno

  reply	other threads:[~2026-06-16 16:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 16:15 [PATCH v2 0/5] workqueue: Detect stalled in-flight workers Breno Leitao
2026-03-05 16:15 ` [PATCH v2 1/5] workqueue: Use POOL_BH instead of WQ_BH when checking pool flags Breno Leitao
2026-03-05 17:13   ` Song Liu
2026-03-05 16:15 ` [PATCH v2 2/5] workqueue: Rename pool->watchdog_ts to pool->last_progress_ts Breno Leitao
2026-03-05 17:16   ` Song Liu
2026-03-05 16:15 ` [PATCH v2 3/5] workqueue: Show in-flight work item duration in stall diagnostics Breno Leitao
2026-03-05 17:17   ` Song Liu
2026-03-05 16:15 ` [PATCH v2 4/5] workqueue: Show all busy workers " Breno Leitao
2026-03-05 17:17   ` Song Liu
2026-03-12 17:03   ` Petr Mladek
2026-03-13 12:57     ` Breno Leitao
2026-03-13 16:27       ` Petr Mladek
2026-03-18 11:31         ` Breno Leitao
2026-03-18 15:11           ` Petr Mladek
2026-03-20 10:41             ` Breno Leitao
2026-06-11 14:50               ` Breno Leitao
2026-06-16 12:38                 ` Petr Mladek
2026-06-16 12:44                   ` Breno Leitao
2026-06-16 12:57                     ` Petr Mladek
2026-06-16 16:48                       ` Breno Leitao [this message]
2026-05-07 10:20   ` Jiri Slaby
2026-05-07 13:11     ` Breno Leitao
2026-05-11  5:21       ` Jiri Slaby
2026-05-13  7:29         ` Thorsten Leemhuis
2026-05-13  8:03           ` Jiri Slaby
2026-03-05 16:15 ` [PATCH v2 5/5] workqueue: Add stall detector sample module Breno Leitao
2026-03-05 17:25   ` Song Liu
2026-03-05 17:39 ` [PATCH v2 0/5] workqueue: Improve stall diagnostics Tejun Heo
2026-03-12 16:38 ` [PATCH v2 0/5] workqueue: Detect stalled in-flight workers Petr Mladek
2026-03-13 12:24   ` Breno Leitao
2026-03-13 14:38     ` Petr Mladek
2026-03-13 17:36       ` Breno Leitao
2026-03-18 16:46         ` Petr Mladek
2026-03-20 10:44           ` Breno Leitao
2026-05-13  8:57     ` Hillf Danton
2026-05-13  8:53 ` Markus Elfring

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=ajF7pwYm08T6SKbC@gmail.com \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=dcostantino@meta.com \
    --cc=jiangshanlai@gmail.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osandov@osandov.com \
    --cc=pmladek@suse.com \
    --cc=song@kernel.org \
    --cc=tj@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