mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [PATCH] workqueue: Log additional details when rejecting work
Date: Fri, 14 Feb 2025 07:16:51 -1000	[thread overview]
Message-ID: <Z696g2IEn_ktHVSM@slm.duckdns.org> (raw)
In-Reply-To: <20250214164349.13694-1-will@kernel.org>

On Fri, Feb 14, 2025 at 04:43:49PM +0000, Will Deacon wrote:
> Syzbot regularly runs into the following warning on arm64:
> 
>   | WARNING: CPU: 1 PID: 6023 at kernel/workqueue.c:2257 current_wq_worker kernel/workqueue_internal.h:69 [inline]
>   | WARNING: CPU: 1 PID: 6023 at kernel/workqueue.c:2257 is_chained_work kernel/workqueue.c:2199 [inline]
>   | WARNING: CPU: 1 PID: 6023 at kernel/workqueue.c:2257 __queue_work+0xe50/0x1308 kernel/workqueue.c:2256
>   | Modules linked in:
>   | CPU: 1 UID: 0 PID: 6023 Comm: klogd Not tainted 6.13.0-rc2-syzkaller-g2e7aff49b5da #0
>   | Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
>   | pstate: 404000c5 (nZcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
>   | pc : __queue_work+0xe50/0x1308 kernel/workqueue_internal.h:69
>   | lr : current_wq_worker kernel/workqueue_internal.h:69 [inline]
>   | lr : is_chained_work kernel/workqueue.c:2199 [inline]
>   | lr : __queue_work+0xe50/0x1308 kernel/workqueue.c:2256
> 
>   [...]
> 
>   |    __queue_work+0xe50/0x1308 kernel/workqueue.c:2256 (L)
>   |  delayed_work_timer_fn+0x74/0x90 kernel/workqueue.c:2485
>   |  call_timer_fn+0x1b4/0x8b8 kernel/time/timer.c:1793
>   |  expire_timers kernel/time/timer.c:1839 [inline]
>   |  __run_timers kernel/time/timer.c:2418 [inline]
>   |  __run_timer_base+0x59c/0x7b4 kernel/time/timer.c:2430
>   |  run_timer_base kernel/time/timer.c:2439 [inline]
>   |  run_timer_softirq+0xcc/0x194 kernel/time/timer.c:2449
> 
> The warning is probably because we are trying to queue work into a
> destroyed workqueue, but the softirq context makes it hard to pinpoint
> the problematic caller.
> 
> Extend the warning diagnostics to print both the function we are trying
> to queue as well as the name of the workqueue.
> 
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Lai Jiangshan <jiangshanlai@gmail.com>
> Link: https://syzkaller.appspot.com/bug?extid=e13e654d315d4da1277c
> Signed-off-by: Will Deacon <will@kernel.org>

Applied to wq/for-6.14-fixes.

Thanks.

-- 
tejun

      reply	other threads:[~2025-02-14 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 16:43 Will Deacon
2025-02-14 17:16 ` Tejun Heo [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=Z696g2IEn_ktHVSM@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=will@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

all inboxes | Powered by JetHome®