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.1-rc3
Date: Wed, 13 May 2026 10:59:41 -1000	[thread overview]
Message-ID: <b35741ac6dd1527bd4601a8eb99bc7ef@kernel.org> (raw)

Hello, Linus.

The following changes since commit 20e81c64c905bd765e69ef07920d2b1130dc79b6:

  workqueue: Annotate alloc_workqueue_va() with __printf(1, 0) (2026-04-29 09:44:16 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git tags/wq-for-7.1-rc3-fixes

for you to fetch changes up to 0143033dc22cdff912cfc13419f5db92fea3b4cb:

  workqueue: Fix wq->cpu_pwq leak in alloc_and_link_pwqs() WQ_UNBOUND path (2026-05-08 07:59:44 -1000)

----------------------------------------------------------------
workqueue: Fixes for v7.1-rc3

- Plug a wq->cpu_pwq leak on the WQ_UNBOUND allocation failure path.

- Fix a cancel_delayed_work_sync() livelock against drain_workqueue()
  caused by the drain/destroy reject path leaving WORK_STRUCT_PENDING set
  with no owner.

----------------------------------------------------------------
Breno Leitao (2):
      workqueue: Release PENDING in __queue_work() drain/destroy reject path
      workqueue: Fix wq->cpu_pwq leak in alloc_and_link_pwqs() WQ_UNBOUND path

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

Thanks.

--
tejun

             reply	other threads:[~2026-05-13 20:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 20:59 Tejun Heo [this message]
2026-05-14 16:40 ` [GIT PULL] workqueue: Fixes for v7.1-rc3 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=b35741ac6dd1527bd4601a8eb99bc7ef@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.