From: Tejun Heo <tj@kernel.org>
To: Breno Leitao <leitao@debian.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com, stable@kernel.org
Subject: Re: [PATCH] workqueue: fix wq->cpu_pwq leak in alloc_and_link_pwqs() WQ_UNBOUND path
Date: Fri, 08 May 2026 08:04:34 -1000 [thread overview]
Message-ID: <0fa37d5a29c847197b3dadc2600623b8@kernel.org> (raw)
In-Reply-To: <20260508-wq_leak-v1-1-4fe76e5c004e@debian.org>
Hello,
On Fri, 08 May 2026 09:22:03 -0700, Breno Leitao wrote:
> For WQ_UNBOUND workqueues, alloc_and_link_pwqs() allocates wq->cpu_pwq
> via alloc_percpu() and then calls apply_workqueue_attrs_locked(). On
> failure it returns the error directly, bypassing the enomem: label
> which holds the only free_percpu(wq->cpu_pwq) in this function.
>
> [...]
Applied to wq/for-7.1-fixes (capitalized the first word of the
subject).
Thanks.
--
tejun
prev parent reply other threads:[~2026-05-08 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 16:22 [PATCH] workqueue: fix wq->cpu_pwq leak in alloc_and_link_pwqs() WQ_UNBOUND path Breno Leitao
2026-05-08 18:04 ` 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=0fa37d5a29c847197b3dadc2600623b8@kernel.org \
--to=tj@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jiangshanlai@gmail.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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