From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 714DA165F16 for ; Fri, 8 May 2026 18:04:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778263475; cv=none; b=G+5E3fbD12Y6cIyKoM+tkStDGzDEUx8cFTVlQhvzX5lf4yOIjr3lbQ7D/vyaAkAqhFIwl+Lb+GCgDzVTh3SSJKpEvq5bdkRwHeVkcpRQb77iRqNb4md5uJUrOpBJHxnabPfK10YETOApWsct+xp6jvhW4tBdRggEVCdLMiuMf9g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778263475; c=relaxed/simple; bh=vk1JOpdPQUwDZYCkDAk1HsGEwvGgCzX5Z1hwjjPZMaI=; h=Date:Message-ID:From:To:Cc:Subject:In-Reply-To:References; b=BgDtXRlFT3K6K982Q81EGJSiyjcpUndJGmjhREiEPWT0ICRs+UqBYG9lCQ1xYZIgRHOsnMZdPBZa9NnlP2BHif5NXpbJV5zeo+9aV+Q5uxvD38s7cPM87RrPF/VVUFeVJEomdKJBo+V4e6cgvAnKv40VmgD6MEom9iTbRiEK1XY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=T+ppF/Co; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="T+ppF/Co" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2D29C2BCC7; Fri, 8 May 2026 18:04:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778263475; bh=vk1JOpdPQUwDZYCkDAk1HsGEwvGgCzX5Z1hwjjPZMaI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=T+ppF/CoqdR/HN4MTxARpT3YhzxNc7L60TkioSHuGcvWo5VbPL+vode0xZY3hlQA9 5BC4gH0C8HAXUzkr2pqg+wp9it2UQ4hBaelI3Rv8UWEZrAxM9vW7EQLmhP3afCecaT gsW/wHaH0ObzLjbVa4vAebichzwJrAy495IEkwk8eZEhc9DqDsW16ZEQEVgOo6PcRc 1J01ZS9frd+wcmV+37uN+Q5Bg6FrPPhF2XWgjsqz48n3v76VhKS2kupSWaiqVcbpI8 yOZ86XuFSjaWTW/nBguhOUiK1NZzhtZIy1VaPJjrmKQ0ka6X9v2MT1t9afv+VXefdJ nB2aOzjbanf4g== Date: Fri, 08 May 2026 08:04:34 -1000 Message-ID: <0fa37d5a29c847197b3dadc2600623b8@kernel.org> From: Tejun Heo To: Breno Leitao , Lai Jiangshan , Dennis Dalessandro 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 In-Reply-To: <20260508-wq_leak-v1-1-4fe76e5c004e@debian.org> References: <20260508-wq_leak-v1-1-4fe76e5c004e@debian.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: 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