All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] workqueue: Fixes for v7.0-rc7
Date: Sun, 12 Apr 2026 07:15:45 -1000	[thread overview]
Message-ID: <fbb535a69fb581aef2c33c60aef52ce6@kernel.org> (raw)

Hello,

This is a fix for a stall which triggers on ordered workqueues when
there are multiple inactive work items during workqueue property changes
through sysfs, which doesn't happen that frequently. While really late,
the fix is very low risk as it just repeats an operation which is
already being performed.

The following changes since commit e398978ddf18fe5a2fc8299c77e6fe50e6c306c4:

  workqueue: Better describe stall check (2026-03-25 05:51:02 -1000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git tags/wq-for-7.0-rc7-fixes

for you to fetch changes up to 703ccb63ae9f7444d6ff876d024e17f628103c69:

  workqueue: Add pool_workqueue to pending_pwqs list when unplugging multiple inactive works (2026-04-01 10:18:22 -1000)

----------------------------------------------------------------
workqueue: Fixes for v7.0-rc7

- Fix incomplete activation of multiple inactive works when unplugging a
  pool_workqueue, where the pending_pwqs list wasn't being updated for
  subsequent works.

----------------------------------------------------------------
Matthew Brost (1):
      workqueue: Add pool_workqueue to pending_pwqs list when unplugging multiple inactive works

 kernel/workqueue.c | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

--
tejun

             reply	other threads:[~2026-04-12 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12 17:15 Tejun Heo [this message]
2026-04-12 17:46 ` [GIT PULL] workqueue: Fixes for v7.0-rc7 pr-tracker-bot

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=fbb535a69fb581aef2c33c60aef52ce6@kernel.org \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.